The following issue has been updated:

    Updater: Bill Carpenter (mailto:[EMAIL PROTECTED])
       Date: Mon, 19 Apr 2004 6:15 PM
    Changes:
             Attachment changed to string-parser-patch.txt
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/SOAP-169?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/SOAP-169

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SOAP-169
    Summary: Message.receiveEnvelope blows up (regression)
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Apache SOAP
   Versions:
             2.3

   Assignee: 
   Reporter: Bill Carpenter

    Created: Mon, 19 Apr 2004 6:12 PM
    Updated: Mon, 19 Apr 2004 6:15 PM

Description:
Diff for /ws-soap/java/src/org/apache/soap/messaging/Message.java between version 1.12 
and 1.13

In the above cited change, there was an inadvertent change from:

  xdb.parse(new InputSource(new StringReader(payloadStr)));

to:

  XMLParserUtils.parse(payloadStr);

The loss of the StringReader wrapper is significant since it leads to "new 
InputSource(payloadStr)".  InputSource constructor with a String is interpreted as a 
systemId, not as the XML blob itself.

This could be fixed either in Message.java or in XMLParserUtils.java.  I have attached 
a patch fixing it in XMLParserUtils.java since the formal parameter names lead me to 
believe the intent is to always pass an XML blob to the parse method (which makes 
sense in the is environment).

BTW, this was discovered when trying to use uddi4j 2.0.2 with Apache SOAP transport.  
It made a very fine explosion while trying to parse responses.

Patch attached.



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira

Reply via email to