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

Jacques Le Roux closed OFBIZ-1957.
----------------------------------

       Resolution: Fixed
    Fix Version/s: Release Branch 4.0
                   SVN trunk
         Assignee: Jacques Le Roux

Thanks Marco for the patch, Bruno for report and BJ for comment,

After some researches I finally commited Marco's patch in trunk revision: 
706692, release4.0  706693

I had a doubt because I thought that maybe in some cases we would not have UTF8 
encoding. 
But as, for now, it's only used in EntitySaxReader.endElement and 
WebToolsServices.parseEntityXmlFile I think it's ok. 

Maybe we could get the encoding from the file. If needed I think it should be 
the way to go. But obviously it's not as simple as this solution...


> Error parsing entity xml file: java.io.CharConversionException: Invalid UTF-8 
> Encoding
> --------------------------------------------------------------------------------------
>
>                 Key: OFBIZ-1957
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1957
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: SVN trunk
>         Environment: SVN trunk rev.694324
>            Reporter: Bruno Busco
>            Assignee: Jacques Le Roux
>             Fix For: SVN trunk, Release Branch 4.0
>
>         Attachments: ImportXmlString.patch
>
>
> While using webtools XML data import feature to import a file containing this:
> <?xml version="1.0" encoding="UTF-8"?>
> <entity-engine-xml>
>   <ElectronicText dataResourceId="ERRORE">
>       <textData>perchè dà errore?</textData>
>   </ElectronicText>
> <entity-engine-xml>
> the following error if given:
> ERROR: Error parsing entity xml file: java.io.CharConversionException: 
> Invalid UTF-8 Encoding
> The same happens if the import textbox is used
> I have found this subject recurring many time in the mailing lists archive 
> but never with a conclusion (AFAIK).
> May be a related issue that could help to fix this is: OFBIZ-1083 where a 
> similar problem was fixed for emails.

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

Reply via email to