Hi Willem,
Thanks for your feedback.
1. I see this dispatch mode as a binding of the JAXWS dispatch API to
the current Camel endpoint model. The JAXWS dispatch gives you the
dispatch API (Dispatch) that allows you transmit SOAPMessage or
Source objects. The Camel CXF endpoint supports the data for
I'll hold until Camel 2.7.0 is done.
William
On 03/11/2011 08:34 PM, Willem Jiang wrote:
I just have a quick look at the patch and has few comments for it.
1. Just a quick question of the Dispatch mode, this dispatch is not
like what we use the JAXWS Dispatch API. What the difference between
I just have a quick look at the patch and has few comments for it.
1. Just a quick question of the Dispatch mode, this dispatch is not like
what we use the JAXWS Dispatch API. What the difference between this
Dispatch and JAXWS Dispatch API ?
We need to write some document to clarify this in ca
Thanks Aki. I'll take a closer look at the problem and commit it as
appropriate over the weekend.
On 03/11/2011 04:09 AM, Aki Yoshida wrote:
Hi William,
Yes. I initialy tried out that approach. And in fact, as you saw, I am
using this dummy class internally and programatically adding its
opera
Hi William,
Yes. I initialy tried out that approach. And in fact, as you saw, I am
using this dummy class internally and programatically adding its
operations to the endpoint. I needed to add the operations because
DummyImpl does not specifiy any information and if there is no
operaiton associated
Hi Aki,
I recalled my suggestion was to try passing a dummy class in the
cxfEndpoint config. It should allow you to send arbitrary payload. I
guess that didn't work? It looks like your patch is doing just that am
I missing something.
I.e.
http://localhost:9000/SoapContext/MyPort";
