The packaged artifact that you see in the hotdeploy dir is the actual component that does the work when you deploy a SU that uses XMPP. This component has all of the dependencies necessary to run the XMPP client. Your SU is just a descriptor so to speak that configures the XMPP component with the host name and login information, etc.
Hope this helps... Chris On Fri, May 23, 2008 at 7:56 AM, jsexton0 <[EMAIL PROTECTED]> wrote: > > Hello and thanks, > Actually, yes I've gone through about everything I can find on this > including the tutorial, and I also built a generic connection to a JBI > instance for my application which went fine (I that case I created and used > an instance in the same JVM as my application). One thing I'm confused > about is that there already is an XMPP package in the hotdeploy directory, > which came with the download, and does seem to activate during the startup. > But it's not at all clear to me how to use that. > > Thanks again > -- > View this message in context: > http://www.nabble.com/XMPP-tp17412424p17426204.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > > -- Chris Custine My Blog :: http://blog.organicelement.com Apache ServiceMix :: http://servicemix.apache.org Apache Directory Server :: http://directory.apache.org
