I was able to fix the ClassCastException by adding my ObjectFactory to the
contextPath, using the Multiple context paths ":" seperator.
That made sure the ElementNSImpl was converted into a JAXBElement.
Unfortunately, it then fails with a NullPointerException on the 1st line of
the try/catch beca
I just tried on a different server, Tomcat 8.0.33.
Same problem, getting
java.lang.ClassCastException:
com.sun.org.apache.xerces.internal.dom.ElementNSImpl cannot be cast to
javax.xml.bind.JAXBElement at Line 195 in Soap11DataFormatAdapter.
It seems to be failing trying decoding
org.xmlsoap.schem
I am using
camel-soap, camel-jaxb, camel-spring 2.17.0
websphere liberty 8.5.5.8.
I do not have camel-saxon on the classpath.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-SoapFault-marshalling-classcast-exception-tp5781986p5782113.html
Sent from the Camel - User
Hi,
I am using the camel-soap project, and working on some exception handling.
I have a SoapFault response which is below.
When camel processes the response, I receive a classcast exception on Line
195 of the Soap11DataFormatAdapter class
ie I get the following error at line: JAXBElement detai
.streamCaching()
.to("jetty:http://localhost:5050/foo?bridgeEndpoint=true";)
.process(inProcessor)
Thanks in advance for any help
-
Cheers
John Mac
--
View this message in context:
http://camel.465427.n5.nabble.com/Gaining-Access-to-the-ServletRe
On 21/11/2011 10:33, Ioannis Canellos wrote:
When I run file transfer happens but the camel does not stop. The funny
thing is whatever files I paste in source folder is transferred to the
target again and again. How to stop the camel running once the transfer is
over?
If I understand the questi
The endpoints are strings - nothing prevents you from externalising such
information (say in a config file) and then build the endpoint urls
based on values in there that you read in at start-up time. Processors
can be equally created 'late'. If the class you are using has state you
can insan
