anchor.diff:  'jms-queue add --queue-address=myQueue --entries=java:jboss/exported/jms/queue/test --durable=false --legacy-entries=java:jboss/exported/jms/queue/legacy1,java:jboss/exported/jms/queue/legacy2'
   
   NOTE: This parameter will be considered only when creating queues and will be ignored for updates.
  +
   |===
   
   
  
positive.code: 
  === EC-JBoss 2.7.1
  
  * Renaming from "CloudBees Flow" to "{CD}"
  
  === EC-JBoss 2.7.0
  
  
negative.code: 
  Unique identifier for a JMS queue per operating mode are as follows:
  
  * For Standalone : 'Queue Name'
  * For Domain : 'Queue Name' and 'Profile'
  
  The expected behavior of this procedure is described below
  
  * If queue does not exist (based on unique identifier) it will be created with specified Queue Name and the list of JNDI names. In case of Domain it will be created based on the specified Profile. Optionally a Queue can be specified to be Durable (default is not durable) and with a Message Selector. The following example shows how the procedure invokes the creation of queue:
  
  'jms-queue --profile=full add --queue-address=newQueueName --entries=java:jboss/exported/jms/queue/test,java:jboss/exported/jms/queue/test2 --durable=false'
  . If queue exists (based on unique identifier) and the specified list of JNDI names differ from existing list of JNDI name for the queue, they will get updated.
  