Re: [Vtd-xml-users] Encoding lost when calling VTDNav.toString(int, int)

[Weachy Z. <wea...@he...>]

Please see VTDNav.toRawString(int, int).

Best Regards,
Weachy

> Hi there,
>
> Firstly I'd like to say that after some initial experimentation with
> VTD-XML it looks really good both in terms of performance and
> usablility. Well done!
>
> I do have a problem however in that when you make a call to
> VTDNav.toString(int, int) any encoding that may have been present inside
> the text of an element eg.
> <xyz>parameterlist?abc=123&amp;def=456&amp;another=something</xyz>
> is returned as:
> <xyz>parameterlist?abc=123&def=456&another=something</xyz>
>
> This causes a problem as if I then pass this entity on to another XML
> parser, in my case JAXB then I receive errors as the content is invalid.
> I could understand this behaviour being correct if I just wanted to
> obtain the text of the element but not the element itself.
>
> I'm guessing this is not by design so wondered if a) someone is aware of
> this and b) if there is a plan to fix it anytime soon?
> I haven't delved into the code myself as yet because I haven't had time
> but thought I would let you know about the problem.
>
> Best Regards,
> James
>
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure
> contains a definitive record of customers, application performance,
> security threats, fraudulent activity, and more. Splunk takes this
> data and makes sense of it. IT sense. And common sense.
> http://p.sf.net/sfu/splunk-novd2d
> _______________________________________________
> Vtd-xml-users mailing list
> Vtd...@li...
> https://lists.sourceforge.net/lists/listinfo/vtd-xml-users
>