Okay, the .jars I'm using at the moment are: camel-core-2.4.0.jar javaee.jar commons-management-1.0.jar commons-logging-1.1.1.jar camel-xmpp-2.4.0.jar smack-3.0.4.jar smackx-3.0.4.jar jaxb-api-2.1.jar jaxb-impl-2.1.12.jar
When I try to listen for XMPP messages I get only one property set on the exchange and no headers in either the in or the out messages. My endpoint is xmpp://localhost/?user=bot&password=botpass exchange.getProperties().keySet().toString() gives me [CamelBinding] exchange.getIn().getHeaders().keySet().toString() gives me [] Same results for an ISP's server as with a localhost server. Am I missing a .jar? I know I'm going kinda minimalist, but I thought I had everything I needed. Don On Sat, Sep 18, 2010 at 2:25 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: > On Sat, Sep 18, 2010 at 5:02 AM, Donald Whytock <dwhyt...@gmail.com> wrote: >> Hi all... >> >> Trying to work with the XMPP component, I find I needed the following .jars: >> >> smack-3.0.4.jar >> smackx-3.0.4.jar >> >> Are these the correct versions to use with Camel 2.4.0? Will these > > Use maven and it will download all the needed files for you. > If not you can check the parent/pom.xml file in Camel source which > lists the versions used at that release time > https://svn.apache.org/repos/asf/camel/tags/camel-2.4.0/parent/pom.xml > > But you can use any compliant jar file as long as it doesn't break :) > So if there is a 3.0.5 jar that works as well then you can use that. > > Looks like 2.4.0 uses > <smack-version>3.1.0</smack-version> > > > >> eventually be included with the Camel download? >> > > No, the download will get too big if Camel included all the .jars for > all the components. > > > If you use maven or osgi then they can automatic download the jars for you. > > >> Don >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus >
