[ https://issues.jboss.org/browse/SRAMP-433?page=com.atlassian.jira.plugin.... ] Brett Meyer commented on SRAMP-433: ----------------------------------- I believe I came up with a solution that will still allow us to run on non-EE app servers, as well as utilize configured JMS/JNDI resources on EE servers. When the s-ramp-events-jms lifecycle starts up, it checks for the existence of a JMS ConnectionFactory and the default S-RAMP topic, both through JNDI. If they exist, it means we're in EE land and things are correctly configured. Simply use them, in addition to any other configured topics/queues. If not, assume we're on Tomcat/Jetty. s-ramp-events-jms will then create an embedded ActiveMQ broker over a TCP port, then programmatically create all topics/queues. Clients can then connect to it in one of two ways: 1.) Simply use the ActiveMQ libs and API. 2.) The ActiveMQ broker provides a lightweight JNDI implementation and automatically exposes the ConnectionFactory. To expose the topics/queues, the *client app* needs to include a jndi.properties file (and ActiveMQ jar) on the classpath. The contents contain something like "topic.[jndi name] = [activemq topic name]". [jndi name] is then available to the client. Other than that properties file, the client is able to use generic JNDI and JMS, without any ActiveMQ APIs. -- This message was sent by Atlassian JIRA (v6.3.1#6329)