Hello,
we need to build a proxy for an external request/reply SOAP web service. This
same service must be offered both unmodified (namespace A) and with a different
namespace B in the message schema. In both cases, some additional routing
decisions must be taken.
For this, we have defined a CX
I don't think the http endpoint can be used to bridge typical soap
webservice calls, as there are some mismatches in the behavior between
the soap protocol and the plain http protocol.
If I understand your scenario, you want to do something like
from-cxf:A ---> to-cxf:A if ...some condition...
fro
bout a namespace mismatch when
using WSDL for namespace A and transforming the incoming message to namespace B?
Thank you,
Dirk
-Ursprüngliche Nachricht-
Von: Aki Yoshida [mailto:elak...@gmail.com]
Gesendet: Dienstag, 20. Januar 2015 11:10
An: users@camel.apache.org
Betreff: Re: Camel-CX
in the CXF processing to which the
> TransformationInInterceptor could be attached so that CXF wouldn't complain
> about a namespace mismatch when using WSDL for namespace A and transforming
> the incoming message to namespace B?
>
> Thank you,
> Dirk
>
>
> -
---
Von: Aki Yoshida [mailto:elak...@gmail.com]
Gesendet: Mittwoch, 21. Januar 2015 15:14
An: users@camel.apache.org
Cc: Sergey Beryozkin
Betreff: Re: Camel-CXF: Problems transforming namespace of incoming message
Hi Dirk,
The transform itself should actually take place with the original interceptor,
gt; -Ursprüngliche Nachricht-
> Von: Aki Yoshida [mailto:elak...@gmail.com]
> Gesendet: Mittwoch, 21. Januar 2015 15:14
> An: users@camel.apache.org
> Cc: Sergey Beryozkin
> Betreff: Re: Camel-CXF: Problems transforming namespace of incoming message
>
> Hi Dirk,
> The tran
Hi Aki, please see below.
> -Ursprüngliche Nachricht-
> Von: Aki Yoshida [mailto:elak...@gmail.com]
> Gesendet: Donnerstag, 22. Januar 2015 22:04
> An: users@camel.apache.org
> Betreff: Re: Camel-CXF: Problems transforming namespace of incoming
> message
>
> 20
