[ 
https://issues.apache.org/jira/browse/AXIS2-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12508525
 ] 

Davanum Srinivas commented on AXIS2-1522:
-----------------------------------------

Amila,

Does the checkin http://svn.apache.org/viewvc?view=rev&revision=551082 fix this 
issue????

thanks,
dims

> Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not 
> in 1.0 stable
> -----------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1522
>                 URL: https://issues.apache.org/jira/browse/AXIS2-1522
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.3
>         Environment: Win2k, SUN JDK 1.5.0_08
>            Reporter: Frank Steimke
>            Assignee: Amila Chinthaka Suriarachchi
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: wsdl.zip
>
>
> Hi,
> attached to this bugreport you will find the WSDL-File with three included 
> Schemafiles for Type-Definitions.
> We are dealing with German eGovernment Applications, so there is a lot of 
> <documentation> with German Text, inkluding German Umlaut. The main 
> Schemafile, which is imported from WSDL, is xmeld-nachrichten.xsd. It was 
> checked by IBMs Schema Quality Checker (SQC) without any Errors.
> Trying to generate Java Code by WSDL2Java works fine with AXIS2 1.0 standard 
> Release, but compilation with "ant jar.server" failed. So I switched to 
> nightly build from October 26.
> Trying to generate Java Code by WSDL2Java fails with a "Malformed UTF-8 
> Character" Exception. The Stacktrace gave some hints about this strange 
> Character. Something seems to be wrong in a documentation where we find a 
> German word with the Fragment 'über...', which is used a lot in these Files.
> So I removed all <annotation> Nodes within all three Schemata, and everything 
> is fine. WSDL2Java generates Code without Exception, and this compiles to the 
> *aar Archive without any Errors.
> This is a minor bug, as i have a Workaround to deal with it. But, besides of 
> resolving the Error, my Question is: why did Axis2 1.0 standard work fine, 
> and the snapshot did not? Did you change the the XML Parser or its 
> configuration?
> Thanks in advance,
> Frank Steimke

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


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to