[ 
https://issues.apache.org/jira/browse/AXIS2C-812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12553413
 ] 

Bill Mitchell commented on AXIS2C-812:
--------------------------------------

After updating through 605623 I have verified that the response messages with 
multiple namespaces are now accepted correctly.  Thank you, Lahiru and Supun.

> guththila parser fails attempting to deallocate unallocated cell if xml 
> message contains more than one namespace
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: AXIS2C-812
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-812
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: guththila
>    Affects Versions: Current (Nightly)
>         Environment: Windows, Visual Studio 2005, guththila validating parser
>            Reporter: Bill Mitchell
>         Attachments: guththila_xml_parser_diff, guththila_xml_parser_diff_2
>
>
> The guththila validating parser fails attempting to deallocate an unallocated 
> cell if the xml message constains more than one namespace.  The issue is that 
> the validating parser allocates one cell of memory to hold an array of 
> namespaces, but that the code that frees the namespaces believes that each 
> array element is a separate cell.  Thus, if the array contains more than one 
> element, the free of the second element fails.  
> One can see the problem when parsing a SOAP response message identifying two 
> namespaces, e.g., one that begins:
> <?xml version="1.0" encoding="UTF-8" ?> 
> - <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:env="http://schemas.xmlsoap.org/soap/envelope/";>
> - <env:Body>
> ...
> This appears to be a problem introduced as part of fix AXIS2C-785 since 1.1.0 
> in the development branch; in 1.1.0 the array was not freed at all.   

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to