I'm still looking for help...
Maybe I made it a bit involved with the test case; here's a simpler example:
java.lang.Exception
# mark the exception as handled
true
# put an error code into the message body
# remove the exception from the exchange
# unfort
Hi all,
I am working on error handling across multiple routes.
client -> route A -> route B
exchange pattern = InOut
I want to process exceptions thrown in route B, by (1) setting a result
field in my message, (2) returning from route B, and then (3) continuing
processing in route A
I can a
The axis consumer works!
Thanks for all the help Willem :)
Regards,
Paul
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-in-tomcat-cannot-process-multiple-parameters-tp4538511p4542653.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Trying the Axis approach now...
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-in-tomcat-cannot-process-multiple-parameters-tp4538511p4541680.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi willem,
I know CXF doesn't support JAX-RPC WSDL, but is there any way to make it
accept RPC/encoded messages?
For instance, has any progress been made on the Aegis databinding?
http://cxf.547215.n5.nabble.com/RPC-Encoded-support-td574781.html
RPC/Encoded Support (cxf-dev)
Could I define an A
Just to put this in context, there is a bigger problem I'm trying to solve...
I have two requirements:
1) deploy my Camel-CXF web service using Tomcat
2) accept calls from a JAX-RPC WSDL-based client
I am currently stuck on #1, because I cannot accept messages with multiple
parameters.
When #1 i
Note: I added logging statements to the CxfConverter and BeanConverter source
files; if these extra statements are confusing, just ignore them.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-cxf-in-tomcat-cannot-process-multiple-parameters-tp4538511p4538992.html
Sent fro
Hi Willem
Here is the tar file.
http://camel.465427.n5.nabble.com/file/n4538980/camel-cxf-tomcat-problem.tar
camel-cxf-tomcat-problem.tar
The log (snipped) reads as follows:
2011-06-30 15:06:04,504 [http-8080-1] TRACE component.cxf.CxfConsumer -
Received CXF Request: {org.apache.cxf.service.S
