I found the error but I don't know how to solve it. So your help is welcome
I have the following route where a XQUERY component is called after a bean.
The headers are lost after calling the component XQUERY
from("file")
.to("bean:authenticate")
.to("directA")
from("direct:A")
.to("bean:Save")
--> Headers are always there
.to("xquery:com/..../qqqq.qxuery)
--> headers are lost (like me)
.to("activemq:queue:A")
Regards,
Charles
cmoulliard wrote:
>
> I continue the tests but it seems that the issue exist when we have the
> combination : bean + jms
>
> The following tests made are conclusive
>
> 1) bean to bean without JMS
>
> setheader --> bean1 (display header : OK) --> bean2 (display header : OK)
>
> 2) from --> jms and from jms to without beans
>
> setheader --> directA --> display header : OK through a processor --> to
> JMS --> from JMS --> display header : OK through a processor
>
>
>
> Claus Ibsen wrote:
>>
>> Hi
>>
>> Can you try combinations:
>> - without the bean endpoints
>> - without the JMS endpoints
>>
>> To verify where the headers is lost?
>>
>>
>> Med venlig hilsen
>>
>> Claus Ibsen
>> ......................................
>> Silverbullet
>> Skovsgårdsvænget 21
>> 8362 Hørning
>> Tlf. +45 2962 7576
>> Web: www.silverbullet.dk
>>
>> -----Original Message-----
>> From: cmoulliard [mailto:[EMAIL PROTECTED]
>> Sent: 10. juli 2008 15:21
>> To: [email protected]
>> Subject: RE: How to avoid to lost Headers add from messages go/from
>> activemq ?
>>
>>
>> I have made a test with vm://localhost:61616?broker.persistent=true and
>> the
>> headers are still lost.
>>
>>
>> cmoulliard wrote:
>>>
>>> Claus,
>>>
>>> I use : Camel 1.4-SNAPSHOT and
>>> vm://localhost:61616?broker.persistent=false
>>>
>>> Is this feature working with "vm" because I see that the documentation
>>> that you refer to is related to "jms" queue ?
>>>
>>> Regards,
>>>
>>> Charles
>>>
>>>
>>> Claus Ibsen wrote:
>>>>
>>>> Hi
>>>>
>>>> What version of Camel are you using? Camel 1.4-SNAPSHOT has had some
>>>> important changes in the JMS component to preserve headers send over
>>>> the
>>>> JMS.
>>>>
>>>> See the wiki that has been updated with information regarding
>>>> restrictions to headers:
>>>> http://activemq.apache.org/camel/jms.html
>>>>
>>>> For example header values must be simple types or primitives such as
>>>> string, numbers etc. You can not send your own Objects as headers.
>>>>
>>>>
>>>>
>>>> Med venlig hilsen
>>>>
>>>> Claus Ibsen
>>>> ......................................
>>>> Silverbullet
>>>> Skovsgårdsvænget 21
>>>> 8362 Hørning
>>>> Tlf. +45 2962 7576
>>>> Web: www.silverbullet.dk
>>>>
>>>> -----Original Message-----
>>>> From: cmoulliard [mailto:[EMAIL PROTECTED]
>>>> Sent: 10. juli 2008 14:30
>>>> To: [email protected]
>>>> Subject: How to avoid to lost Headers add from messages go/from
>>>> activemq
>>>> ?
>>>>
>>>>
>>>> Hi,
>>>>
>>>> How can we avoid to lost headers when messages go to/from a ActiveMq ?
>>>>
>>>> e.g.
>>>>
>>>> from("")
>>>> .setHeader("God", myGodIs)
>>>> .to("direct:A")
>>>>
>>>> from("direct:A")
>>>> .to("bean:doWhatYouWant") --> the key "God" is there
>>>> .to("activeMq:queue:myqueue")
>>>>
>>>> from("activeMq:queue:myqueue")
>>>> .to("bean:dontDoWhatYouWant") --> the key "God" is lost
>>>>
>>>> Is there a trick to define a header as a global header and can be found
>>>> from
>>>> any endpoint ?
>>>>
>>>> Regards,
>>>>
>>>> Charles
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/How-to-avoid-to-lost-Headers-add-from-messages-go-from-activemq---tp18381854s22882p18381854.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://www.nabble.com/How-to-avoid-to-lost-Headers-add-from-messages-go-from-activemq---tp18381854s22882p18382835.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/How-to-avoid-to-lost-Headers-add-from-messages-go-from-activemq---tp18381854s22882p18385579.html
Sent from the Camel - Users mailing list archive at Nabble.com.
