Hello,

I created a test case not related to JMeter and submitted:

- https://github.com/x-stream/xstream/issues/51

Jörg from XStream already answered:
https://github.com/x-stream/xstream/issues/51#issuecomment-210155359

------------------------------------------------------------------------------------------------------------------------------------------------------

well, your source code already contains invalid UTF-8 characters (assuming
your Java files are UTF-8 encoded). This means that already the compiler
produces garbage when creating the class file.

However, not every character is valid in XML (and it depends on the XML
version). Some parsers do not care (like Xpp3), some do (all StAX) drivers.
See valid characters in XML spec 1.0
<http://www.w3.org/TR/2006/REC-xml-20060816/#charsets> and XML spec 1.1
<http://www.w3.org/TR/2006/REC-xml11-20060816/#charsets>, and XStream's FAQ
<http://x-stream.github.io/faq.html#XML_null_char>.

------------------------------------------------------------------------------------------------------------------------------------------------------

So I think we should for now revert then see what we do with this in the
future.


Regards
Philippe

On Thu, Apr 14, 2016 at 9:30 PM, Philippe Mouawad <
philippe.moua...@gmail.com> wrote:

> HI Milamber,
> How was this plan created ?
>
> For me it's not a blocker as the XML is wrong. But if we end up thinking
> it is a blocker, then let's revert the code and wait for 3.1 to "fix" this
> although I don't see how it can be.
> Regards
>
> On Thu, Apr 14, 2016 at 9:10 PM, Milamber <milam...@apache.org> wrote:
>
>> Hello,
>>
>> Please see the Bug 58679, I've found a regression with the changes from
>> xstream/xpp librairies.
>>
>> Error : missing class
>> com.thoughtworks.xstream.converters.ConversionException: : ParseError at
>> [row,col]:
>> etc.
>>
>> If I revert the associated commits, my simple script works.
>>
>> Milamber
>>
>> https://bz.apache.org/bugzilla/show_bug.cgi?id=58679
>>
>>
>>
>
>
> --
> Cordialement.
> Philippe Mouawad.
>
>
>


-- 
Cordialement.
Philippe Mouawad.

Reply via email to