[
https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Mitchell reopened AXIS2C-963:
----------------------------------
This change has broken incoming SOAP messages that begin with an xml
declaration. What is happening is that guththila interprets the CR-LF after
the <?xml ... > declaration as GUTHTHILA_SPACE (AXIOM_XML_READER_SPACE) to be
returned. But axiom_stax_builder_next_with_token diagnoses an error and
returns -1 when the space token cannot be attached as text to the last node
(there is no last node) by axiom_stax_builder_create_om_text(). The end result
is that the client sees an error number 187, SOAP message does not contain a
SOAP envelope element.
> Guththila neglects spacing and formatting between nodes whereas libxml2
> preserves it.
> -------------------------------------------------------------------------------------
>
> Key: AXIS2C-963
> URL: https://issues.apache.org/jira/browse/AXIS2C-963
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila, xml/parser
> Reporter: Senaka Fernando
> Assignee: Senaka Fernando
> Fix For: 1.3.0
>
>
> Guththila neglects spacing and formatting between nodes. This behavior
> contradicts to that of libxml2. Thus, If I open a file then deserialize it
> and build our OM Model, then print it to the terminal, I have lost the
> formatting in the file. This is because the parser simply filters out the
> whitespace. This behavior would make our parsing inconsistent.
> Regards,
> Senaka
--
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]
