You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Amar K (JIRA)" <ji...@apache.org> on 2018/08/27 17:38:00 UTC

[jira] [Created] (CXF-7828) Increases size of the payload(xml as a string) results - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint. - Error

Amar K created CXF-7828:
---------------------------

             Summary: Increases size of the payload(xml as a string) results - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint. - Error
                 Key: CXF-7828
                 URL: https://issues.apache.org/jira/browse/CXF-7828
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.7.7
         Environment: Production
            Reporter: Amar K
         Attachments: image-2018-08-27-10-34-12-193.png

SOAP WSDL

Generated client stub using the apache cxf - wsdl2java feature.

When invoking the SOAP webservice using the SOAP client stubs generated it results an error - A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint. 

Upon further analysis we identified *increased size of the xml string results above error*. For the *lower size of the xml string the service works fine*.

Below is the snippet of the code we are using when observed in debug the *port* object refers to "org.apache.cxf.jaxws.JaxWsClientProxy" class pointing to the client-stub class(FASPSoap).

 

 
{code:java}
String orderxml = "Order xml constructed as a String";
final Transfer201210 ss = new Transfer201210();
ss.addPort(Transfer201210.Transfer201210Port, "Transfer201210Binding", soapapiurl);
final FASPSoap port = ss.getTransfer201210Port();
final SubmitRequest r = new SubmitRequest();
r.setDefinition(orderxml);
final SubmitResponse _submit__return = port.submit(r);
{code}
 

 

As per the wsdl the SubmitRequest object accepts the definition attribute as a String. See below.

!image-2018-08-27-10-34-12-193.png!

 

Please help us know if this a "memory intensive" related operation issue. And how should it be addressed.

 

Thanks

Amar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)