axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Takehiko Ishii (JIRA)" <axis-...@ws.apache.org>
Subject [jira] Commented: (AXIS-2459) Encoding incompatibility about deliverables of WSDL2Java between Axis 1.2.x and 1.3
Date Fri, 14 Apr 2006 08:59:00 GMT
    [ http://issues.apache.org/jira/browse/AXIS-2459?page=comments#action_12374484 ] 

Takehiko Ishii commented on AXIS-2459:
--------------------------------------

I have tried buliding patched axis and confirmed -E option is valid and solve the problem.
Thank you!

Which version of axis will include this fix?

> Encoding incompatibility about deliverables of WSDL2Java between Axis 1.2.x and 1.3
> -----------------------------------------------------------------------------------
>
>          Key: AXIS-2459
>          URL: http://issues.apache.org/jira/browse/AXIS-2459
>      Project: Apache Axis
>         Type: Bug

>   Components: WSDL processing
>     Versions: 1.3
>  Environment: Windows XP SP2 Japanese, Sun JDK 1.5.0
>     Reporter: Takehiko Ishii
>  Attachments: AXIS-2459.patch
>
> The encoding of deliverables generated by WSDL2Java contained in Axis 1.3 are UTF-8.

> There is an encoding incompatibility between Axis 1.3 and 1.2.x, Axis 1.2.1 and before
generates deliverables using a system encoding, for example MS932 on Japanese Windows. This
behavior seems affected by the fix of AXIS-2122 .
> Would it be possible to add a command line option to WSDL2Java which specify to use a
system encoding as an encoding of deliverables?
> System encoding is often used as encoding of java file, so this seems useful for users
who intend to migrate axis 1.2.x to 1.3.
> Steps:
> 0. create WSDL file using DBCS characters in message element name, portType name, binding
name, operation name and so on.
> 1. set jar files under Axis install directory to AXISCLASSPATH 
> 2. execute the following to generate web service client code on Japanese Windows 
>    java -cp %AXISCLASSPATH% org.apache.axis.wsdl.WSDL2Java XXXX.wsdl
> 3. check the encoding of generated client code
> 4. execute the following to generate web service skelton code on Japanese Windows
>    java -cp %AXISCLASSPATH% org.apache.axis.wsdl.WSDL2Java -s -S true XXXX.wsdl
> 5. check the encoding of skelton code
> Current behavior:
> The all deliverables have UTF-8 encoding. It seems WSDL2Java generates deliverables using
UTF-8 encoding as fixed (hard-coded) value.
> Axis 1.2.1 and before generates deliverables using System encoding, so there is an incompatibility
between axis 1.3 and 1.2.1.

-- 
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


Mime
View raw message