Yes, I removed the header, and that works fine.
However carrying all exchange headers over to HTTP headers makes it very
difficult to carry over "route payload" if the CXF endpoint was not the last
endpoint. However, I am getting the feeling it is not going to be easily
possible to respond back t
You can remove the unwanted headers.
On Tue, Feb 5, 2013 at 2:09 PM, panzerhans wrote:
> I've been able to work a bit more on this topic. Here is what is happening.
>
> The exchange headers used in the Camel part propagates into HTTP headers. I
> wasen't aware of this.
>
> Websphere is very stri
I've been able to work a bit more on this topic. Here is what is happening.
The exchange headers used in the Camel part propagates into HTTP headers. I
wasen't aware of this.
Websphere is very strict about the content of the headers and a data object
that I was using carried an illegal sequence i
No change when wrapping the string inside an object.
I have two other contract first webservices. Those does not display the
above behaviour. So I am going to pick up the WSDL file and rewrite the
spring wiring.
--
View this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0
Thank you for your reply.
For the WSDL: Yes, return type is correct.
I have tried both staying away from putting anything into the exchange.out
and instead manipulating the in body. This ended with a NPE:
2013-01-24 14:45:33,003 WARN WebContainer : 0
|cxf.phase.PhaseInt
On Wed, Jan 23, 2013 at 9:02 PM, panzerhans wrote:
> I have created a CXF webservice and exposed it with camel. The webservice is
> code first (JSR-181) annotated Java class, springed up in my application
> context.
>
> The class looks like this:
>
> @WebService(name="DataExport", serviceName="Dat
NB: Camel version: 2.6.0 (latest possible on Websphere 6.1).
--
View this message in context:
http://camel.465427.n5.nabble.com/Websphere-6-1-0-45-Unable-to-return-data-from-a-camel-cxf-component-POJO-mode-tp5726083p5726084.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I have created a CXF webservice and exposed it with camel. The webservice is
code first (JSR-181) annotated Java class, springed up in my application
context.
The class looks like this:
@WebService(name="DataExport", serviceName="DataExport",
targetNamespace="com.somecompany.dataexport.v1")
publi
