Hi Monica,
I just committed a patch[1] for the CAMEL-2091[2] which could make your
#parser work in Camel trunk (2.1-SNAPSHOT).
[1]http://svn.apache.org/viewvc?view=revision&revision=829724
[2]https://issues.apache.org/activemq/browse/CAMEL-2091
Willem
Monica_G wrote:
Hello Willem,
Thank yo
Hello Willem,
Thank you for your reply and looking into the issue.
I just wanted to clarify that I'm not certain that passing in the Properties
config file will solve my ResourceNotFoundException. I think it may be the
way to go, but I don't know for sure.
Thanks,
Monica
--
View this messa
The template should be
${body}
..
I just committed a quick fix for the CAMEL-2092.
Willem
Willem Jiang wrote:
Oh, the OrderXml template should be
${Body}
...
BTW, I just wrote a simple test against the latest camel-velocity
component. There is a bug[1] of camel-veloci
Oh, the OrderXml template should be
${Body}
...
BTW, I just wrote a simple test against the latest camel-velocity
component. There is a bug[1] of camel-velocity and a quick fix is coming up.
[1]https://issues.apache.org/activemq/browse/CAMEL-2092
Willem
Willem Jiang wrote:
Hi Mo
Hi Monica,
I think we can introduce a new parameter which accepts the velocity's
properties configuration.
I just created a JIRA[1] for it, before we resolved this issue, I don't
think current camel-velocity supports this configuration
Before that , I think you may try to let the message th
