Glad this works! but your earlier one should also work...there was a support
for dynamic uri added to wiretap as part of 2.16, Not sure if it has a
issue.
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/org-apache-camel-NoTypeConversionAvailableException-whi
gt; Regards,
> -Yogesh
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://camel.465427.n5.nabble.com/org-apache-camel-NoTypeConversionAvailableException-while-using-WireTap-tp5783486p5783525.html
> T
by any chance your body of the exchange is null ?
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/org-apache-camel-NoTypeConversionAvailableException-while-using-WireTap-tp5783486p5783525.html
Sent from the Camel - Users mailing list archive at Nabble.com.
//camel.465427.n5.nabble.com/org-apache-camel-NoTypeConversionAvailableException-while-using-WireTap-tp5783486p5783497.html
> To unsubscribe from org.apache.camel.NoTypeConversionAvailableException
> while using WireTap, click here
> <http://camel.465427.n5.nabble.com/template/Na
Hi,
I am suspecting the LoggerService bean has a method which takes in param, is
it a User defined Object which is sent as a param to the method ?
Regards,
-Yogesh
--
View this message in context:
http://camel.465427.n5.nabble.com/org-apache-camel-NoTypeConversionAvailableException-while-usin
Hello,
I am encountering NoTypeConversionAvailableException while using
WireTap in my routes.
An excerpt from the route is as follows,
.bean("requestUpdater", "setRequestToInProcessState")
.wireTap("bean:loggerService")
.newExchangeBody(constant("Some log message."))
.end()
.enri