Apache
/
activemq-artemis
mirror of https://github.com/apache/activemq-artemis.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
activemq-artemis/docs/user-manual/en/tomcat.md

39 lines
1.5 KiB
Markdown
Raw Normal View History

NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
# Apache Tomcat Support
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
## Resource Context Client Configuration
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
Apache ActiveMQ Artemis provides support for configuring the client, in the tomcat resource context.xml of Tomcat container.
This is very similar to the way this is done in ActiveMQ 5.x so anyone migrating should find this familiar.
Please note though the connection url and properties that can be set for ActiveMQ Artemis are different please see [Migration Documentation](https://activemq.apache.org/artemis/migration/)
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
### Example of Connection Factory
```xml
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
<Context>
...
<Resource name="jms/ConnectionFactory" auth="Container" type="org.apache.activemq.artemis.jms.client.ActiveMQConnectionFactory" description="JMS Connection Factory"
factory="org.apache.activemq.artemis.jndi.JNDIReferenceFactory" brokerURL="tcp://localhost:61616" />
...
</Context>
````
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
### Example of Destination (Queue and Topic)
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
```xml
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
<Context>
...
<Resource name="jms/ExampleQueue" auth="Container" type="org.apache.activemq.artemis.jms.client.ActiveMQQueue" description="JMS Queue"
factory="org.apache.activemq.artemis.jndi.JNDIReferenceFactory" address="ExampleQueue" />
...
<Resource name="jms/ExampleTopic" auth="Container" type="org.apache.activemq.artemis.jms.client.ActiveMQTopic" description="JMS Topic"
factory="org.apache.activemq.artemis.jndi.JNDIReferenceFactory" address="ExampleTopic" />
...
</Context>
````
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
## Example Tomcat App
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
NO-JIRA review docs for content, style, & format
2018-03-08 15:46:38 -05:00
A sample Tomcat app with the container context configured as an example can be seen here:
ARTEMIS-1516 - Ensure JNDI via Tomcat Resource works Apply fix so that when using JNDI via tomcat resource it works. Replace original extract of JNDIStorable taken from Qpid, and use ActiveMQ5's as fits better to address this issue. (which primary use case is users migrating from 5.x) Refactored ActiveMQConnectionFactory to externalise and turn into reference by StringRefAddr's instead of custom RefAddr which isnt standard. Refactored ActiveMQDestinations similar Refactored ActiveMQDestination to remove redundent and duplicated name field and ensured getters still behave the same
2017-11-03 22:26:39 -04:00
/examples/features/sub-modules/tomcat