topic Re: cCXF component with payload mode in Talend Studio

cCXF component with payload mode

Anonymous — Sat, 16 Nov 2024 09:09:34 GMT

Is there an example that shows how to make a SOAP call in a Route with cCXF component with PAYLOAD mode selected?

Re: cCXF component with payload mode

Loko — Mon, 23 Oct 2017 12:40:34 GMT

The only requirement is to have some text in your message body that fits the WSDL for your service/operation.

What is your issue ?

Re: cCXF component with payload mode

Anonymous — Mon, 23 Oct 2017 16:59:57 GMT

So I need to provide in the body to the cCXF component the body of the SOAP envelope?

Where do I put all the elements that are in my SOAP body element

<S:Body xmlns:ns2=...>

...

</S:Body>

Re: cCXF component with payload mode

Loko — Mon, 23 Oct 2017 17:11:04 GMT

Yes, only the body, as your component will auto create the soap enveloppe by itself.

Re: cCXF component with payload mode

Anonymous — Mon, 23 Oct 2017 17:36:51 GMT

When I select RAW in the component and send entire SOAP to the component I get back 0 from the service.

When I tried with only SOAP body and select PAYLOAD mode I get an error.

How do I add all the XML elements from the SOAP?

Re: cCXF component with payload mode

Loko — Tue, 24 Oct 2017 09:56:34 GMT

You will have to be more precise if you want some help : what error do you get ?

I confirm sending the soap body in exchange body and letting the cxf component do the rest works fine.

Re: cCXF component with payload mode

Anonymous — Tue, 24 Oct 2017 10:27:56 GMT

this is what I send to the exchange body:

  <S:Body xmlns:ns2="....">
    <ns2:upload>
      <arg0>
        <credentials>
          <password>...</password>
          <username>...</username>
        </credentials>
        <document>
          <content>j</content>
          <name>1.xml</name>
        </document>
        <documentType>12</documentType>
        <formatType>19</formatType>
      </arg0>
    </ns2:upload>
  </S:Body>

and the error I get

com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix "S"
 at [row,col {unknown-source}]: [1,61]
	at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:614)
...

the route for testing

Re: cCXF component with payload mode

Loko — Tue, 24 Oct 2017 10:29:53 GMT

remove de s:body tags

and be careful with namespaces, that have to suit exactly your WSDL

Re: cCXF component with payload mode

Anonymous — Tue, 24 Oct 2017 13:19:14 GMT

After I remove starting and closing Body tag I get

[WARN ]: org.apache.camel.component.cxf.CxfEndpoint - Error finding the start element.
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace prefix "ns2"
at [row,col {unknown-source}]: [1,16]
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:614)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:487)

Re: cCXF component with payload mode

Loko — Tue, 24 Oct 2017 13:32:03 GMT

this is what I told you :be careful with your namespaces.
Try to remove them from your body stuff

Re: cCXF component with payload mode

Anonymous — Tue, 24 Oct 2017 13:39:24 GMT

I accidently clikced accept as a solution.

My exchange body now looks like this

    <upload>
      <arg0>
        <credentials>
          <password>...</password>
          <username>...</username>
        </credentials>
        <document>
          <content>j</content>
          <name>1.xml</name>
        </document>
        <documentType>12</documentType>
        <formatType>19</formatType>
      </arg0>
    </upload>

And now I get this error:

org.apache.cxf.binding.soap.SoapFault: Cannot find dispatch method for {}upload
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.unmarshalFault(Soap11FaultInInterceptor.java:86)
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:52)
	at org.apache.cxf.binding.soap.interceptor.Soap11FaultInInterceptor.handleMessage(Soap11FaultInInterceptor.java:41)

Re: cCXF component with payload mode

Loko — Tue, 24 Oct 2017 13:44:44 GMT

again, if you want help, give people as many data as you can. We still haven't see your WSDL.

Just be sure your CXF is correctly parameterized with the url, the wdsl, the button to choose en operation and to automatically parameter the other cxf parameters.

There are many samples on internet for using Talend cxf

Re: cCXF component with payload mode

Anonymous — Tue, 24 Oct 2017 13:51:36 GMT

Why do you need to see the WSDL?

When I put SOAP bellow into the exchange body and switch the component to RAW, I get ok response from the service:

 <S:Body xmlns:ns2="....">
    <ns2:upload>
      <arg0>
        <credentials>
          <password>...</password>
          <username>...</username>
        </credentials>
        <document>
          <content>j</content>
          <name>1.xml</name>
        </document>
        <documentType>12</documentType>
        <formatType>19</formatType>
      </arg0>
    </ns2:upload>
  </S:Body>

Re: cCXF component with payload mode

Anonymous — Tue, 24 Oct 2017 14:27:48 GMT

here is the wsdl https://crossnet-test.crossinx.com:9444/crossnetws/UploadService?wsdl

Re: cCXF component with payload mode

Anonymous — Thu, 26 Oct 2017 11:08:53 GMT

Hi,

I did a test with:

<?xml version="1.0" ?>
<tns:upload xmlns:tns="http://upload.service.ws.findxnet.com/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<arg0>
<aaLookupName>A</aaLookupName>
<aaLookupValue>A</aaLookupValue>
<document>
<content>A</content>
<name>A</name>
</document>
<documentType/>
<formatType/>
<userAccount xsi:type="tns:userAccountVO"/>
</arg0>
</tns:upload>

It looks fine. I get this reply:

<ns2:uploadResponse xmlns:ns2="http://upload.service.ws.findxnet.com/" xmlns="http://schemas.xmlsoap.org/soap/envelope/"><return><code>-2</code><details>User is not authorized to perform this operation. Check if documentType, formatType or probably lookup are incorrect. A:A</details></return></ns2:uploadResponse>

Eric

Re: cCXF component with payload mode

Anonymous — Thu, 26 Oct 2017 15:17:28 GMT

This setup worked for me:

    <ns2:upload xmlns:ns2="http://upload.service.ws.findxnet.com/">
      <arg0>
        <credentials>
          <password>...</password>
          <username>...</username>
        </credentials>
        <document>
          <content>j</content>
          <name>1.xml</name>
        </document>
        <documentType>12</documentType>
        <formatType>19</formatType>
      </arg0>
    </ns2:upload>