Keep in mind that the configuration for the broker would need to change if it's in another JVM as the example only supports in-vm connections.
Justin ----- Original Message ----- From: "Justin Bertram" <jbert...@apache.com> To: users@activemq.apache.org Sent: Tuesday, January 12, 2016 1:18:37 PM Subject: Re: Client and server artifacts in Spring JMS example. You're mostly right. Everything but the "securityManager" and "EmbeddedJms" beans are for the client. Justin ----- Original Message ----- From: "Derek Mahar" <derek.ma...@gmail.com> To: users@activemq.apache.org Sent: Tuesday, January 12, 2016 1:14:12 PM Subject: Client and server artifacts in Spring JMS example. From https://github.com/apache/activemq-artemis/blob/master/examples/features/standard/spring-integration/src/main/resources/spring-jms-beans.xml, would it be accurate to separate the beans into the following lists of client and server components? Client - connectionFactory (org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory) - exampleQueue (org.apache.activemq.artemis.jms.client.ActiveMQQueue) - MessageSender (org.apache.activemq.artemis.jms.example.MessageSender) Server - securityManager (org.apache.activemq.artemis.spi.core.security.ActiveMQJAASSecurityManager) - EmbeddedJms (org.apache.activemq.artemis.integration.spring.SpringJmsBootstrap) - listener (org.apache.activemq.artemis.jms.example.ExampleListener) - listenerContainer (org.springframework.jms.listener.DefaultMessageListenerContainer) The purpose of this exercise would be to isolate the server from the client components in order to embed the server components alone into another server process. Derek
