Welcome Guest! Log in
×

Notice

The forum is in read only mode.
Due to some maintenance operations, stambia.org will be switched to read-only mode during the 13th November. It will be possible to read and download, but impossible to post on the forums or create new accounts. For any question please contact the support team.

Topic-icon Question error :com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException

More
05 Apr 2019 12:00 #1 by Sylvie INGABIRE
Sylvie INGABIRE created the topic: error :com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException
Hello,

I have this error when I execute an sql to parameters, with accents in a string value.
Example of the script :

<sqlToParameters>
<parameter name="../p_custtype_code" type="String">
select
case
when '${~/BusinessUnitCode}$' = '1' then 'réassort'
end
from %x{$MYTABLE/tech:physicalPath()}x%
</parameter>
</sqlToParameters>


Because of the accent (é) in 'réassort', I have the error : com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException: Octet 2 de la séquence UTF-8 à 3 octets non valide.
I only have this error when executing the sql to parameters on a runtime on windows. With a same version runtime on unix, I don't have the error.

Runtime version : S17.6.5

How could I fix this?

Thanks.
More
05 Apr 2019 18:15 #2 by Thomas BLETON
Thomas BLETON replied the topic: error :com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException
Hi,

The expression for the Sql To Parameters is based on XML.
XML often requires special characters to be encoded.
Try to replace "é" with "é" and it should work.

I think that the error does not occur on Linux because it is not the same java vendor / version.

Note : we plan to provide in the future a new version of this Sql To Parameters action which will not have this kind of requirement.
More
08 Apr 2019 15:22 - 08 Apr 2019 15:25 #3 by Sylvie INGABIRE
Sylvie INGABIRE replied the topic: error :com.sun.org.apache.xerces.internal.impl.io.MalformedByteSequenceException
Hello,

It does work when using
"&#xE9;"

Thanks

Sylvie
Last Edit: 08 Apr 2019 15:25 by Sylvie INGABIRE.