There is no difference - the standalone and embedded broker are the
same. What we can do for connivence - is start/stop an embedded
broker as part of the vm:// transport. However, there is nothing to
stop you starting a broker in your app - and connecting to it
directly (in which case it's not controlled by the life-cycle of the
connecting client(s). A lot of our test cases work this way - e.g.
http://svn.apache.org/viewvc/activemq/trunk/activemq-core/src/test/
java/org/apache/activemq/perf/SimpleTopicTest.java?
revision=564271&view=markup
look at the createBroker() method
cheers,
Rob
http://rajdavies.blogspot.com/
On Oct 12, 2007, at 12:43 PM, Motl wrote:
Hi,
I want to know the difference between the separate broker app and the
embedded broker, featurewise.
What isn't supported in the embedded broker?
--
View this message in context: http://www.nabble.com/embedded-broker-
features-tf4613136s2354.html#a13173737
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
