[jboss-jira] [JBoss JIRA] Commented: (GPD-184) gpd.xml incorrect with non-ascii characters like Chinese

Fri Nov 23 05:28:18 EST 2007

    [ http://jira.jboss.com/jira/browse/GPD-184?page=comments#action_12388864 ] 

Matthias Hanisch commented on GPD-184:
--------------------------------------

I faced the same problem today.
processdefinition.xml is managed by WST directly and they do it correct.
gpd.xml is managed manually in designer plugin (AbstractContentProvider) and there is nowhere the encoding taken into account.

For the short term, I hard-coded reading and writing of gpd.xml to UTF-8 encoding.
To achieve this, you have to add the encoding in getBytes() call in saveToInput() and in InputStreamReader constructor in addNotationInfo().
Of course, a complete fix would analyze the encoding of the gpd.xml file and respect that, but that's beyond my knowledge. Probably it works by just using wst methods.

Note: after this change, you cannot get the notation info from already corrupted files. So it is better to remove non-ascii characters from node name attributes before applying.

> gpd.xml incorrect with non-ascii characters like Chinese
> --------------------------------------------------------
>
>                 Key: GPD-184
>                 URL: http://jira.jboss.com/jira/browse/GPD-184
>             Project: JBoss jBPM GPD
>          Issue Type: Bug
>          Components: jpdl
>    Affects Versions: jBPM jPDL Designer 3.1.0.SP1
>         Environment: Eclipse WTP 1.5 with JDK 1.6
> Windows XP Home SP2
>            Reporter: Ryan Wong
>         Assigned To: Koen Aers
>
> When named the node with non-ascii character like ??
> the generated gdp.xml is human unreadable. (not proper UTF-8 file)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira