On Mon, Sep 20, 2010 at 9:03 PM, Donald Whytock <dwhyt...@gmail.com> wrote: > Using Smack 3.1.0, both standalone and with Camel. Smack supplies > From and To values, Body and packet type (message vs. info/query vs. > presence). Camel gives me Body and that's about it. > > I would expect to see the From and To set in the > exchange.getIn().getHeaders(). > > In Camel I don't see non-message packets at all. Is this a bug or a > feature? Should there be options for enabling non-message packets, > perhaps with the packet type as a property? Or is this exceeding > Camel's mission statement?
It could be a feature currently not in the camel-xmpp component. We love contributions. http://camel.apache.org/contributing.html So please go ahead and see if you can implement it. > > On Mon, Sep 20, 2010 at 10:14 AM, Donald Whytock <dwhyt...@gmail.com> wrote: >> The body's coming through. Just no headers or properties. >> >> My next step was going to be to try the smack library directly, to >> make sure it's doing its job. If it is I can have a look at the >> component. >> >> >> On Sun, Sep 19, 2010 at 2:38 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>> On Sat, Sep 18, 2010 at 9:58 AM, Donald Whytock <dwhyt...@gmail.com> wrote: >>>> Okay...libraries updated. Still not seeing properties or headers. >>>> >>> >>> Could you check some of the unit tests in camel-xmpp. Maybe there is a >>> hint there, or maybe the camel-xmpp component lacks a feature. >>> We love contributions and if people got the time to dig into it that >>> would be great. >>> >>> Can you at least see the body? So at least some data is being transferred? >>> >>> >>>> Don >>>> >>>> On Sat, Sep 18, 2010 at 3:03 AM, Claus Ibsen <claus.ib...@gmail.com> wrote: >>>>> Hi >>>>> >>>>> These are the jars from the 2.5-SNAPSHOT. You need to use the ones >>>>> which listed as compile. >>>>> >>>>> [INFO] The following files have been resolved: >>>>> [INFO] aopalliance:aopalliance:jar:1.0:test >>>>> [INFO] commons-logging:commons-logging:jar:1.1.1:test >>>>> [INFO] commons-logging:commons-logging-api:jar:1.1:compile >>>>> [INFO] junit:junit:jar:4.8.1:test >>>>> [INFO] log4j:log4j:jar:1.2.16:test >>>>> [INFO] org.apache.camel:camel-core:jar:2.5-SNAPSHOT:compile >>>>> [INFO] org.apache.camel:camel-spring:jar:2.5-SNAPSHOT:test >>>>> [INFO] org.apache.camel:camel-test:jar:2.5-SNAPSHOT:test >>>>> [INFO] org.fusesource.commonman:commons-management:jar:1.0:compile >>>>> [INFO] org.igniterealtime.smack:smack:jar:3.1.0:compile >>>>> [INFO] org.igniterealtime.smack:smackx:jar:3.1.0:compile >>>>> [INFO] org.springframework:spring-aop:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-asm:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-beans:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-context:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-core:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-expression:jar:3.0.4.RELEASE:test >>>>> [INFO] org.springframework:spring-tx:jar:3.0.4.RELEASE:test >>>>> >>>>> >>>>> On Sat, Sep 18, 2010 at 9:00 AM, Donald Whytock <dwhyt...@gmail.com> >>>>> wrote: >>>>>> 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 >>>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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 >>>>> >>>> >>> >>> >>> >>> -- >>> 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 >>> >> > -- 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
