[jira] Reopened: (AXIS2C-857) guththila parser drops xml:id attributes from incoming elements

["Bill Mitchell (JIRA)" <ji...@apache.org>]

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

Bill Mitchell reopened AXIS2C-857:
----------------------------------


Probably thanks to Lahira and I cooperating to work on the patch, we ended up with a version in diff.txt that introduced the logic to create an xml: namespace declaration twice in guththila_init().  Obviously one of the two identical blocks of following code needs to be removed.  
Starting with
    temp_name = guththila_token_create(GUTHTHILA_XML_NAME,0,strlen(GUTHTHILA_XML_NAME),
                                        1,0,0,env);
    temp_tok = guththila_token_create(GUTHTHILA_XML_URI,0,strlen(GUTHTHILA_XML_URI),
                                      1,0,0,env);
through the end of the new code at:
            e_namesp = NULL;
        }
        return GUTHTHILA_FAILURE;
    }


> 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
>            Assignee: Dinesh Premalal
>            Priority: Minor
>             Fix For: 1.2.1
>
>         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