[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2635) Provider can't send back (echo) received soap message correctly

Alessio Soldano (JIRA) jira-events at lists.jboss.org
Wed Apr 29 10:20:46 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBWS-2635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alessio Soldano updated JBWS-2635:
----------------------------------

    Workaround Description: 
Rewrite the endpoint this way:
public SOAPMessage invoke(SOAPMessage request)
   {
      System.out.println("PROVA");
      SOAPMessage message = null;
      try
      {
         String str = DOMWriter.printNode(request.getSOAPPart().getEnvelope(), true);
         InputStream in = new ByteArrayInputStream(str.getBytes());
         MessageFactory factory = MessageFactory.newInstance();
         message = factory.createMessage(null, in);
      }
      catch (Exception e)
      {
         throw new RuntimeException(e);
      }
      return message;
   }

IOW, re-create a new message instead of sending back the received one.
               Description: 
Invoking the org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage endpoint (which sends back the received message instance) using tools like SOAPUi with a message like

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prov="http://org.jboss.ws/provider">
   <soapenv:Header/>
   <soapenv:Body>
      <prov:user>
         <string>?</string>
         <qname>?</qname>
      </prov:user>
   </soapenv:Body>
</soapenv:Envelope>

causes a truncated message to go on the wire, even if the message is correctly logged by the MessageTrace.
Exchanging the message above using the related testcase (org.jboss.test.ws.jaxws.samples.provider.ProviderMessageTestCase) does not reproduce the issue.

  was:
Invoking the org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage endpoint using tools like SOAPUi with a message like

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prov="http://org.jboss.ws/provider">
   <soapenv:Header/>
   <soapenv:Body>
      <prov:user>
         <string>?</string>
         <qname>?</qname>
      </prov:user>
   </soapenv:Body>
</soapenv:Envelope>

causes a truncated message to go on the wire, even if the message is correctly logged by the MessageTrace.
Exchanging the message above using the related testcase (org.jboss.test.ws.jaxws.samples.provider.ProviderMessageTestCase) does not reproduce the issue.



> Provider can't send back (echo) received soap message correctly
> ---------------------------------------------------------------
>
>                 Key: JBWS-2635
>                 URL: https://jira.jboss.org/jira/browse/JBWS-2635
>             Project: JBoss Web Services
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions:  jbossws-native-3.1.1
>            Reporter: Alessio Soldano
>
> Invoking the org.jboss.test.ws.jaxws.samples.provider.ProviderBeanMessage endpoint (which sends back the received message instance) using tools like SOAPUi with a message like
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:prov="http://org.jboss.ws/provider">
>    <soapenv:Header/>
>    <soapenv:Body>
>       <prov:user>
>          <string>?</string>
>          <qname>?</qname>
>       </prov:user>
>    </soapenv:Body>
> </soapenv:Envelope>
> causes a truncated message to go on the wire, even if the message is correctly logged by the MessageTrace.
> Exchanging the message above using the related testcase (org.jboss.test.ws.jaxws.samples.provider.ProviderMessageTestCase) does not reproduce the issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jbossws-issues mailing list