[
https://issues.apache.org/jira/browse/AXIS2C-963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568079#action_12568079
]
Bill Mitchell commented on AXIS2C-963:
--------------------------------------
Senaka, it's a good question whether a better fix is available. I considered
whether to implement a change down in axiom_stax_builder_create_om_text(), but
it doesn't know whether the text is whitespace or not. And I like the fact
that non whitespace text before the root element will be diagnosed as an error.
To address your concern, one could replicate the test against lastnode in
axiom_stax_builder_next_with_token(), before it calls
axiom_stax_builder_create_om_text(). Looking at the code again, I actually
like that fix better than the one I put in, as it would preserve the ability to
detect other errors, and would prevent the error being posted to the
environment and then ignored.
> 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]
