On Wed, May 28, 2008 at 2:03 PM, jsexton0 <[EMAIL PROTECTED]> wrote: > > That makes sense. > Sorry this is such a slow process, but I still don't see how some things > work. 1) When I built with maven, where do the resulting binaries land? 2) > Does that rebuild servicemix-xmpp-3.2.1-installer.zip?
Maven puts all compiled classes, packages, etc. into the target dir for the given project. The servicemix-xmpp-3.2.1-installer.zip file is the JBI component. Put that file into the SMX hotdeploy directory. That way when you start up SMX the servicemix-xmpp component will be running in memory but doing nothing. You need to tell it what to do by deploying a configuration to it. This is accomplished by creating a SU and SA and dropping the SA into the hotdeploy directory. The JBI container will extract the SU from the SA and send the SU to the servicemix-xmpp component and it will use the configuration. Have you read the What Is JBI? FAQ item yet? http://servicemix.apache.org/what-is-jbi.html That document provides a quick intro to JBI and will help you understand the big picture so you can get started. Bruce -- perl -e 'print unpack("u30","D0G)[EMAIL PROTECTED]&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' Apache ActiveMQ - http://activemq.org/ Apache Camel - http://activemq.org/camel/ Apache ServiceMix - http://servicemix.org/ Apache Geronimo - http://geronimo.apache.org/ Blog: http://bruceblog.org/
