I have two endpoints, one derived from jaxws:endpoint and other via Provider
interface. Both have different service ports, names but share same binding.
Both are wired with WS-Security policy.
CXF enabled w/ WS-Security:
http://localhost/reportService/"; />
Finally after many hours of testing, the issue was resolved. Camel route was
not adding SOAP tags to the calls intended to reach external webservice.
--
View this message in context:
http://camel.465427.n5.nabble.com/CXF-Camel-Proxy-Bug-tp5436846p5437208.html
Sent from the Camel - Users mailing
I am trying to use the camel-cxf-proxy example with CXF2.5.1-CAMEL 2.6.0 with
no luck. The only difference between the example and my setup, is I use
PAYLOAD mode and run the realwebservice on an external webcontainer.
The route receiver complains, it cannot covert CxfPayload to InputStream. Is
th
True, but I do not understand why "out" is empty, whereas the same external
endpoint when hit directly fetches response.
-
Expected from direct invocation outside camel route:
http://schemas.xmlsoap.org/soap/envelope/";>
http://services.reporting.mycomp.com/2011/10/outputs";
With the help of this forum I was able to overcome my previous issue related
to external webservice invocation. However, as a continuation to the same
problem when a successful response is returned by this external endpoint, I
encounter this error in my camel context.
I try to Message out = exchan
Thanks for your help, finally I think I'm getting a handle on this issue
after applying suggested change. The only open item is, how do I catch or
get to know the exception thrown by my external service. Both
Exchange.getException and exchange.getProperty(Exchange.EXCEPTION_CAUGHT,..)
returns null.
I see a different error, but it still does not get into my context
gracefully. I can do a log:output and get back into the context successfully
only if I do not encounter a Fault/Exception on my external service.
http://camel.apache.org/schema/spring";>
I'm using JAX-WS, and to step back I'm on CXF2.4.1+Camel 2.4.0 (My bad on
version typo). My use case is to receive client PAYLOAD, process SOAP header
and route to external service for it to process the body and return
response. The issue is, when this external service throws an
Exception/Fault; it
Our application server is still dependent on Java5. The reason for me to move
to Camel 2.9.0 is to address "status code 500" error thrown when my route
endpoint throws an exception. I believe this was addressed in 2.8.3 and
above. Am i correct? If so, Is Camel 2.8.3 compliant with Java 5, and shoul
I was successful integrating CXF2.4.1-Camel2.8.0, however when I moved to the
newer version of CXF2.5.1 and Camel 2.9.0, I see issues related to
CamelTransportFactory. UnsupportedClassVersionError. These dependency jars
work with older version. Am i missing any?
Dependency Jars included in my proj
10 matches
Mail list logo
