[jira] Updated: (ODE-472) utf-8 encoding is handled incorrectly within xslt stylesheets

[Alexey Ousov (JIRA)]

     [ 
https://issues.apache.org/jira/browse/ODE-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alexey Ousov updated ODE-472:
-----------------------------

    Attachment: ODE-472-ful.patch

Full path for this bug report attached

- Xml encoding for external files is determined by Xml parser itself (external 
files are returned as streams).
- In order to keep compiler compatibility, xslt stylesheets still loaded from 
String. To determine correct encoding, this tip was used: 
http://www.ibm.com/developerworks/library/x-tipsaxxni/ . This has no external 
dependencies, and uses bundled Java xml parser if none provided. But this 
require Java 5 version for "org.xml.sax.ext.Locator2" interface.

After applying patch, all affecting BPEL processes should be recompiled 
(because xslt body is stored inside compiled BPEL process)

> utf-8 encoding is handled incorrectly within xslt stylesheets
> -------------------------------------------------------------
>
>                 Key: ODE-472
>                 URL: https://issues.apache.org/jira/browse/ODE-472
>             Project: ODE
>          Issue Type: Bug
>          Components: BPEL Runtime
>    Affects Versions: 1.2
>            Reporter: Alexey Ousov
>         Attachments: ODE-472-ful.patch, ODE-472-quickfix.patch, 
> ODE-472.patch, test1.par.zip
>
>
> The bug occurs when UTF-8 encoded symbols appear either within stylesheet 
> itself or inside documents referenced with document() function. All such 
> symbols are encoded twice.
> So if we have in xslt something like:
> <xsl:value-of select="&#00e0;" />
> which is UTF-8 encoded as "C3 A0" in result node we will have sequence "C3 83 
> C2 A0" which is UTF-8 encoded "&#00c3;&#00a0;".
> The case of bug is XslRuntimeUriResolver class, which reads files to string 
> without parsing file encoding. I made quick fix, which fixes only document() 
> function with xpath 1.0 runtime. Deeper investigation is needed, so hopefully 
> full fix will be available after New Year.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.