WildFly HornetQ-Based Messaging Subsystem - Deploying a JMS Destination

Internal

• Messaging Subsystem Configuration

Deployment

<subsystem xmlns="urn:jboss:domain:messaging:1.2">
   <hornetq-server>
      ...
      <jms-destinations>
         <jms-queue name="test">
            <entry name="queue/test"/>
            <durable>false</durable>
         </jms-queue>
         <jms-topic name="test">
            <entry name="topic/test"/>
         </jms-topic>
     </jms-destinations>
     ...
   </hornetq-server>
</subsystem>

If you want the queue to be available remotely, for the use of a remote JMS client, for example, add an extra "java:jboss/exported/..." as follows:

      <jms-destinations> 
         <jms-queue name="test">
            <entry name="queue/test"/>
            <entry name="java:jboss/exported/queue/test"/>
            <durable>false</durable>
         </jms-queue>
      </jms-destinations>

Security

The permission to perform a certain operation on an address (send, receive), etc. is dictated by the role the connection user belongs to. The permission configuration is set in the <security-settings> section:

The default configuration is:

    <security-settings>
        <security-setting match="#">
            <permission type="send" roles="guest"/>
            <permission type="consume" roles="guest"/>
            <permission type="createNonDurableQueue" roles="guest"/>
            <permission type="deleteNonDurableQueue" roles="guest"/>
        </security-setting>
    </security-settings>

For more details on messaging security see:

Messaging Concepts - Security