Mailing-List: contact axis-c-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C Developers List" <axis-c-dev@ws.apache.org>
Message-ID: <10091182.1201135835002.JavaMail.jira@brutus>
Date: Wed, 23 Jan 2008 16:50:35 -0800 (PST)
From: "Bill Mitchell (JIRA)" <jira@apache.org>
To: axis-c-dev@ws.apache.org
Subject: [jira] Updated: (AXIS2C-857) guththila parser drops xml:id
 attributes from incoming elements
In-Reply-To: <7745739.1198819543194.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/AXIS2C-857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Mitchell updated AXIS2C-857:
---------------------------------

    Attachment: diff2.txt

Lahira, it's a nice start on a patch; it's certainly in the right direction.  In testing it I uncovered a few minor coding errors.   In guththila_init(), (a) the declarations needed to come at the start of the block, (b) the namespace size is getting setting wrong, as it needs strlen(), sizeof is rounding up to the next multiple of the machine word, (c) the code did not handle out-of-memory on the token creates.  In guththila_token_create, (d) it was allocating the wrong length of for the string and the token structure, and (e) it was not actually returning the pointer to the allocated token to the caller.  

In the attached diff2.txt, I corrected the coding errors and the client app now sees the xml:id attributes on the elements and can process them.  Thanks for getting this started.  

> guththila parser drops xml:id attributes from incoming elements
> ---------------------------------------------------------------
>
>                 Key: AXIS2C-857
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-857
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: guththila
>    Affects Versions: Current (Nightly)
>         Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
>            Reporter: Bill Mitchell
>            Priority: Minor
>         Attachments: diff.txt, diff2.txt
>
>
> The XML specification allows an element to carry an xml:id attribute without the xml namespace being declared explicitly.  In fact, if the xml namespace is declared, it must match http://www.w3.org/XML/1998/namespace.  When the namespace is not declared explicitly, it appears that the guththila parser discards the incoming xml:id attributes without including them in the om.  
> For example, I receive a response message from a service that begins:
> <env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:fw="http://frameware.xcentrisity.com/services/">
> <env:Body>
> <fw:getExemplarResponse responseMessage="master exemplar provided." name="customer" supportedMethods="browse browseNext browsePrevious create update delete retrieve">
> <exemplar handle="master">
> <cr-customer-record xml:id="Q375" type="xsd:string">
> <cr-customer-id xml:id="Q376" type="xsd:string">
> </cr-customer-id>
> ...
> When linked with libxml, the client code sees two attributes, a type attribute and an xml:id attribute, attached to the element nodes.  When linked with the guththila parser, only the type attribute is present.  

-- 
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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org