You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@camel.apache.org by titexe <ti...@yahoo.Fr> on 2010/02/16 09:59:27 UTC
Problem with velocity component
Hello,
using the velocity component don't respect the case matching of all fields
of the header (JMS Header + Properties)
For example: the exchange of properties JMSCorrelationID change the case
matching, after using velocity component, it puts the property in lowercase
jmscorrelationid.
there's any way to solve this problem?
Thank you in advance
titexe
--
View this message in context: http://old.nabble.com/Problem-with-velocity-component-tp27605243p27605243.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with velocity & freemarker and Stringtemplate components
Posted by Willem Jiang <wi...@gmail.com>.
Hi
Please fill a JIRA with your test case, if you already have a patch,
that will be great, we will fix it before the next release of Camel.
Willem
titexe wrote:
> I have tested the component Camel-stringtemplate for the same thing
>
> I discovered another problem: the component Camel-stringtemplate loses all
> fields properties.
> worse than the component velocity or freemarker:)
>
> Thank you in advance
>
> titexe
>
>
>
> titexe wrote:
>> I tried to test the component freemarker instead of a velocity component,
>> but unfortunately there's the same the problem of case sensitivity for
>> fields properties of the message header.
>>
>> thank you inadvance,
>>
>> titexe
>>
>>
>> Claus Ibsen-2 wrote:
>>> On Tue, Feb 16, 2010 at 9:59 AM, titexe <ti...@yahoo.fr> wrote:
>>>> Hello,
>>>>
>>>> using the velocity component don't respect the case matching of all
>>>> fields
>>>> of the header (JMS Header + Properties)
>>>>
>>>> For example: the exchange of properties JMSCorrelationID change the case
>>>> matching, after using velocity component, it puts the property in
>>>> lowercase
>>>> jmscorrelationid.
>>>>
>>>> there's any way to solve this problem?
>>>>
>>> Well you could dig into this and see what Velocity does. For example
>>> fire up a debugger and check the problem and help pin point the issue.
>>> Then you could try to fix it yourself and submit a patch.
>>>
>>> For example you can also create a simple unit test without JMS that
>>> just set a header like JMSCorrelationID and have it routed through
>>> velocity and see what the case of the header is now. Then create a
>>> JIRA ticket and attach your sample.
>>>
>>>
>>>
>>>> Thank you in advance
>>>>
>>>> titexe
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Problem-with-velocity-component-tp27605243p27605243.html
>>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>> --
>>> 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
>>>
>>>
>>
>
Re: Problem with velocity & freemarker and Stringtemplate
components
Posted by titexe <ti...@yahoo.Fr>.
I have tested the component Camel-stringtemplate for the same thing
I discovered another problem: the component Camel-stringtemplate loses all
fields properties.
worse than the component velocity or freemarker:)
Thank you in advance
titexe
titexe wrote:
>
> I tried to test the component freemarker instead of a velocity component,
> but unfortunately there's the same the problem of case sensitivity for
> fields properties of the message header.
>
> thank you inadvance,
>
> titexe
>
>
> Claus Ibsen-2 wrote:
>>
>> On Tue, Feb 16, 2010 at 9:59 AM, titexe <ti...@yahoo.fr> wrote:
>>>
>>> Hello,
>>>
>>> using the velocity component don't respect the case matching of all
>>> fields
>>> of the header (JMS Header + Properties)
>>>
>>> For example: the exchange of properties JMSCorrelationID change the case
>>> matching, after using velocity component, it puts the property in
>>> lowercase
>>> jmscorrelationid.
>>>
>>> there's any way to solve this problem?
>>>
>>
>> Well you could dig into this and see what Velocity does. For example
>> fire up a debugger and check the problem and help pin point the issue.
>> Then you could try to fix it yourself and submit a patch.
>>
>> For example you can also create a simple unit test without JMS that
>> just set a header like JMSCorrelationID and have it routed through
>> velocity and see what the case of the header is now. Then create a
>> JIRA ticket and attach your sample.
>>
>>
>>
>>> Thank you in advance
>>>
>>> titexe
>>> --
>>> View this message in context:
>>> http://old.nabble.com/Problem-with-velocity-component-tp27605243p27605243.html
>>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>>
>>>
>>
>>
>>
>> --
>> 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
>>
>>
>
>
--
View this message in context: http://old.nabble.com/Problem-with-velocity-component-tp27605243p27606955.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with velocity component
Posted by titexe <ti...@yahoo.Fr>.
I tried to test the component freemarker instead of a velocity component, but
unfortunately there's the same the problem of case sensitivity for fields
properties of the message header.
thank you inadvance,
titexe
Claus Ibsen-2 wrote:
>
> On Tue, Feb 16, 2010 at 9:59 AM, titexe <ti...@yahoo.fr> wrote:
>>
>> Hello,
>>
>> using the velocity component don't respect the case matching of all
>> fields
>> of the header (JMS Header + Properties)
>>
>> For example: the exchange of properties JMSCorrelationID change the case
>> matching, after using velocity component, it puts the property in
>> lowercase
>> jmscorrelationid.
>>
>> there's any way to solve this problem?
>>
>
> Well you could dig into this and see what Velocity does. For example
> fire up a debugger and check the problem and help pin point the issue.
> Then you could try to fix it yourself and submit a patch.
>
> For example you can also create a simple unit test without JMS that
> just set a header like JMSCorrelationID and have it routed through
> velocity and see what the case of the header is now. Then create a
> JIRA ticket and attach your sample.
>
>
>
>> Thank you in advance
>>
>> titexe
>> --
>> View this message in context:
>> http://old.nabble.com/Problem-with-velocity-component-tp27605243p27605243.html
>> Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>
>
>
> --
> 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
>
>
--
View this message in context: http://old.nabble.com/Problem-with-velocity-component-tp27605243p27606502.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with velocity component
Posted by Claus Ibsen <cl...@gmail.com>.
On Tue, Feb 16, 2010 at 9:59 AM, titexe <ti...@yahoo.fr> wrote:
>
> Hello,
>
> using the velocity component don't respect the case matching of all fields
> of the header (JMS Header + Properties)
>
> For example: the exchange of properties JMSCorrelationID change the case
> matching, after using velocity component, it puts the property in lowercase
> jmscorrelationid.
>
> there's any way to solve this problem?
>
Well you could dig into this and see what Velocity does. For example
fire up a debugger and check the problem and help pin point the issue.
Then you could try to fix it yourself and submit a patch.
For example you can also create a simple unit test without JMS that
just set a header like JMSCorrelationID and have it routed through
velocity and see what the case of the header is now. Then create a
JIRA ticket and attach your sample.
> Thank you in advance
>
> titexe
> --
> View this message in context: http://old.nabble.com/Problem-with-velocity-component-tp27605243p27605243.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
--
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