BTW, CAMEL-2544 and CAMEL-2495 are issues for throwing Application SOAP
Fault when the CXF endpoint is in PAYLOAD mode and no SEI (serviceClass)
is provided.
William Tam wrote:
I think it is hard to workaround the problem. If you can rebuild
just the camel-cxf component yourself, you can mer
I think it is hard to workaround the problem. If you can rebuild just
the camel-cxf component yourself, you can merge the fix (the change is
quite small). Please make sure you pick up
https://issues.apache.org/activemq/browse/CAMEL-2544 too.
Willem Jiang wrote:
I'm afraid CXF interceptor c
I'm afraid CXF interceptor can help you to do that,as we setup some
customer interceptor when the camel-cxf endpoint working in PAYLOAD
dataformat.
Can you try the latest Camel to see if the Error still there?
BTW, is there any stack trace in the log that can help us trace the issue ?
Willem
Hi,
For generalization I had written the endpoint as ("http:requestset"), but
this is actually a custom endpoint which internally uses CXF to create the
web-service endpoint.
Its working fine when sending normal response but only when soap fault needs
to be returned does is not work.
We can't
Hi,
I tried setting the Soap Fault in exchange.setException() but that also is
not working. Still getting the soap envelope with empty body.
Just wondering if you are using camel 2.0.0 too, coz then I can be sure this
issue is not due to the specific version.
Thanks,
Himanshu
Jim Talbut wro
Hi,
Is the from("http:requestset") a CXF endpoint or other something ?
I just went through the CxfConsumer code of camel trunk, it should be
able to deal with the fault message that you set in the ErrorProcessor.
If you can't upgrade the Camel version, I'm afraid you need to buy a
customer su
Hi,
I'm no expert on this, but have you tried setting it as an exception
instead?
This is working for me:
public class SoapFaultConversionProcessor implements Processor
{
private static final String ANONYMOUS_FAULT_STRING = "An unexpected
error has occured.";
private static final Logger
Hi Willem,
Thanks for your response.
I am having the following groovy route:
from("http:requestset")
.onException(Exception.class)
.handled(true)
.processRef('ErrorProcessor').end()
.process(new ValidateRequestProcessor());
Here the 'ValidateRequestProcessor' validates the reques
Hi,
Can I have a look at your Camel route?
And which camel-cxf DataFormat are you using ?
If you are using PAYLOAD DataFormat, I'm afraid you need to use Latest
Camel 2.3.0 SNAPSHOT. As William Tam just added a enhancement for it[1]
[1]https://issues.apache.org/activemq/browse/CAMEL-2495
HiS
