I just went through http://incubator.apache.org/servicemix/how-stuff-works.html#HowStuffWorks-sedaflow ,
and it seems that SEDA flow , which is the default , does not use queues but a ConcurrentHashMap. Is this correct ? Does it mean that for a default installation which used the SEDA flow , there is no need for ActiveMQ ? ActiveMQ would be required only when using a JMSFlow or JCAFlow .. Is this understanding correct ? thanks Pat apinke wrote: > > Hi all, > > I am using SM version 3.0 snapshot and deployed as a WAR in tomcat5.0. > To test how I can configure SM to use an external broker , I first removed > the activemq.xml and then removed all refernces to the broker in the > applicationContext.xml. What I expected was that SM should not start as it > requires ActiveMQ and no brokers have been defined. > > But to my surprise it started up fine and even processed all the requests > !...Can anyone explain how its actually working. I enabled logging for > org.apache.activemq to DEBUG but I dont see any output related to > ActiveMQ. > > I am very curious to know how its working ! > I was expected to see errors as no activemq broker has been defined and > then I was going to add an "broker" reference to an external broker. > > Heres my applicationContext.xml : > > <?xml version="1.0" encoding="UTF-8"?> > <beans xmlns="http://xbean.org/schemas/spring/1.0"; > xmlns:sm="http://servicemix.apache.org/config/1.0"; > xmlns:amq="http://activemq.org/config/1.0";> > > > > <!-- the JBI container --> > <sm:container id="jbi" > monitorInstallationDirectory="false" > monitorDeploymentDirectory="false" > > > > <sm:activationSpecs> > > <sm:activationSpec componentName="httpBinding" > service="test:httpBinding" > > destinationService="test:test-service"> > <sm:component> > <bean > class="org.apache.servicemix.components.http.HttpInOutBinding"> > <property name="defaultInOut" value="true"/> > <property name="marshaler"> > <bean > class="com.its.test.esb.core.MyHttpMarshaler"/> > </property> > </bean> > </sm:component> > </sm:activationSpec> > > <sm:activationSpec componentName="test-service" > service="test:test-service"> > <sm:component> > <bean class="com.its.test.esb.core.TestEchoComponent"> > > </bean> > </sm:component> > </sm:activationSpec> > </sm:activationSpecs> > </sm:container> > > </beans> > > thanks > Pat > > > > -- View this message in context: http://www.nabble.com/ServiceMix-still-working-when-no-ActiveMQ-broker-defined...how--tf3326690s12049.html#a9250193 Sent from the ServiceMix - User mailing list archive at Nabble.com.
