Here it is:
Caused by: org.xmlpull.v1.XmlPullParserException: entity reference names
can not start with character '&' (position: START_TAG seen
...sVerifyTagsArray(a.getVerifyTagsDefault())}if(a.debug||(a.verify&&...
@1:1722019)
at org.xmlpull.mxp1.MXParser.parseEntityRef(MXParser.java:2212)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1275)
at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)
at
com.thoughtworks.xstream.io.xml.XppReader.pullNextEvent(XppReader.java:109)
... 17 more
-- Stefan
On 14.11.2012 14:05, Stefan Bühlmann wrote:
> Hi Jörg,
>
> how do I extract the native parser exception?
>
> I am using xpp3_min-1.1.4c.
>
> -- Stefan
>
>
> On 14.11.2012 13:57, Jörg Schaible wrote:
>> Hi Stefan,
>>
>> Stefan Bühlmann wrote:
>>
>>> Hi Jörg,
>>>
>>> thank you for your post. Complete stack trace:
>>
>> [snip]
>>
>> I am still missing the stack trace of the causing exception(s). XStream only
>> catches and wraps a native parser exception.
>>
>> Also I cannot reproduce this behavior. I've enhanced XStream's unit tests
>> for an entity declaration within a CDATA section and all supported XML
>> parsers succeed, the entity is always ignored (as it has to be).
>>
>> So, which Xpp3 version are you using?
>>
>> - Jörg
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe from this list, please visit:
>>
>> http://xircles.codehaus.org/manage_email
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
