Currently, the core container depends on some ActiveMQ classes, so you need to keep the jars. But you should be able to not start any ActiveMQ broker, which should solve your problem I guess.
On 10/9/06, johper <[EMAIL PROTECTED]> wrote:
Hi, We deploy Servicemix as a war file in JBoss. Unfortunately ActiveMQ's Derby (bundled in Servicemix) collision with another deployed product's Derby in JBoss. How can we make this work? Reconfigure Servicemix's ActiveMQ Derby so it uses same Derby as the other product? Or can we turn ActiveMQ off for Servicemix? Since we use ST-flow do Servicemix need ActiveMQ? tia Johan -- View this message in context: http://www.nabble.com/Servicemix-as-war-in-JBoss-tf2409765.html#a6716740 Sent from the ServiceMix - User mailing list archive at Nabble.com.
-- Cheers, Guillaume Nodet
