Ok, so it should work then, which is what I was hoping was the answer. Basically, with the stand alone servicemix, I drop my jars into hot deploy, and after they are deployed, I start up a little test harness I have which makes an activemq connection to servicemix, to send test messages. When I drop my component into the servicemix war, and tried to run the test harness, I get a connection refused:
Caused by: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616. I'm assuming that even with no jbi components of my deployed, I still shouldn't have a connection problem right? This makes me thing I'm missing something. I had noticed the war seems to not include the majority of configuration files that the standalone one includes. On Tue, May 13, 2008 at 4:22 PM, Guillaume Nodet <[EMAIL PROTECTED]> wrote: > On Tue, May 13, 2008 at 10:05 PM, Ryan Moquin <[EMAIL PROTECTED]> > wrote: > > I'm still trying to work through getting the servicemix war up and > running > > with our jbi components. I had to move a bunch of jar files into > tomcat's > > lib/ext to make the classes that JBI components depend on in the > standalone > > servicemix distribution classpath. But I'm not sure if I got > everything > > since my JBI components still don't work. The problem I'm hitting now, > is > > that it looks like the servicemix war doesn't start up an activemq > broker? > > Or if it does, it starts it on a different port than the standalone one > > does? I tried importing the activemq.xml config file from the > standalone > > version, but that doesn't help. > > What kind of problems did you hit in doing so ? It should work if you put > the > needed jars in the war. > > > > > I'm a little puzzled on how to get the servicemix war to have the same > > functionality as the stand alone distribution. Has anyone successfully > done > > this? > > > > Thanks! > > > > Ryan > > > > > > -- > Cheers, > Guillaume Nodet > ------------------------ > Blog: http://gnodet.blogspot.com/ >
