[ http://issues.apache.org/jira/browse/AXIS2-1522?page=all ]
Frank Steimke updated AXIS2-1522:
---------------------------------
Attachment: wsdl.zip
WSDL File with imported Schema. The documentation wich causes the error is part
of the Schema (don``t know which one in particular). This results in a
Malformed UTF-8 Character Exception when doing WSDL2Java. Remove all
annotations in the Schema, an everything is fine.
> Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not
> in 1.0 stable
> -----------------------------------------------------------------------------------------
>
> Key: AXIS2-1522
> URL: http://issues.apache.org/jira/browse/AXIS2-1522
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: codegen
> Affects Versions: nightly
> Environment: Win2k, SUN JDK 1.5.0_08
> Reporter: Frank Steimke
> Priority: Minor
> 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.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
