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.

  <cxf:cxfEndpoint id="serviceEndpoint"
                   address="http://localhost:9000/SoapContext/MyPort";
                   endpointName="s:MyPort"
                   serviceName="s:MyService"
                   serviceClass="org.apache.cxf.jaxws.support.DummyImpl">
    <cxf:properties>
      <entry key="dataFormat" value="PAYLOAD"/>
    </cxf:properties>
  </cxf:cxfEndpoint>

Also, could you elaborate on the purpose of addInvokeOperation()?

Thanks,
William

On 03/10/2011 01:19 PM, Aki Yoshida wrote:
Hi,
I added the CXF dispatch mode to the Camel CXF endpoint so that I can
ran SOAP intermediary/gateway scenarios over a single CXF endpoint
with some CXF features enabled.

I attached the patch file and unit test files to CAMEL-3778.

In short, you can configure your endpoint like

   <cxf:cxfEndpoint id="serviceEndpoint"
                   address="http://localhost:9000/SoapContext/MyPort";
                   endpointName="s:MyPort"
                   serviceName="s:MyService"
                   bus="#bus">
     <cxf:properties>
       <entry key="dataFormat" value="PAYLOAD"/>
     </cxf:properties>
   </cxf:cxfEndpoint>

and send arbitrary SOAP messages over this endpoint while you CXF bus
configuraiton can add some features to your processing.

I would appreciate if you can give me your feedback.

Thanks.

Regards, aki

Reply via email to