[
https://issues.apache.org/jira/browse/AXIS2C-859?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563814#action_12563814
]
Lahiru Gunathilake commented on AXIS2C-859:
-------------------------------------------
Thanks Bill for the comment.Here's my idea on your comment,
First:This is very similar thing what i have done and only difference is
there's no memory allocation in this method.However if it's better to avoid
another memory allocation i will do it in that way.
Second : This is not much clear for me.If you can explain some more that'll be
great.
Third Forth Fifth: +1for all three ideas. I'll implement these in that way.
Regards
Lahiru
> guththila parser fails to handle escape sequences for ampersand, less than,
> greater than
> ----------------------------------------------------------------------------------------
>
> Key: AXIS2C-859
> URL: https://issues.apache.org/jira/browse/AXIS2C-859
> Project: Axis2-C
> Issue Type: Bug
> Components: guththila
> Affects Versions: Current (Nightly)
> Environment: Windows XP, Visual Studio 2005, guththila parser, libcurl
> Reporter: Bill Mitchell
> Attachments: diff.txt
>
>
> When an incoming message contains within text the escaped ampersand sequence,
> "&", this sequence is being passed to the client as raw text without
> being converted to the single ampersand character. Clearly, this action must
> take place at the level of the parser, as only the parser knows whether it is
> seeing simple text, and conversion is required, or text embedded in a CDATA
> section, where conversion is not allowed. I have tested the build with the
> libxml parser, and of course the libxml parser behaves correctly: the text
> passed to the client contains only the single ampersand character, not the
> escaped sequence. (See section 2.4 of XML 1.0 spec.)
> Looking at the code, I expect the same problem occurs with all escaped
> sequences, less than and greater than as well as ampersand, on both input and
> output. I also don't see where CDATA sections are handled, but as I am not
> seeing CDATA in the messages from the service I am hitting, I have not tested
> this case.
--
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]
