axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Updated: (AXIS2-1522) Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable
Date Wed, 31 Jan 2007 14:54:07 GMT


Davanum Srinivas updated AXIS2-1522:

    Assignee: Deepal Jayasinghe

> Malformed UTF-8 Character Exception in WSDL2Java only in nightly build, not in 1.0 stable
> -----------------------------------------------------------------------------------------
>                 Key: AXIS2-1522
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: nightly
>         Environment: Win2k, SUN JDK 1.5.0_08
>            Reporter: Frank Steimke
>         Assigned To: Deepal Jayasinghe
>            Priority: Minor
>         Attachments:
> 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
> 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
> 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:
For additional commands, e-mail:

View raw message