[ 
http://issues.apache.org/jira/browse/AXIS-2001?page=comments#action_66646 ]
     
Will Lauer commented on AXIS-2001:
----------------------------------

I'm not sure I agree with this resolution. To me, it seems like a bug if using 
slightly different JVM minor versions produces different output. 

It seems like the code is depending on the ordering of items being returned 
from a hash table. Since hash tables make no guarentes about the ordering of 
their items, this seems like a bug. If Sun were to implement HashMap natively, 
I could easily see how byte ordering on two different platforms could result in 
different mappings in the hash table. If the code depends on ordering, it must 
either order the items itself (like the Axis 1.2RC3 code did) or depend on some 
other data structure that a hash table.



> Generated stubs differ between Solaris and Windows
> --------------------------------------------------
>
>          Key: AXIS-2001
>          URL: http://issues.apache.org/jira/browse/AXIS-2001
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: 1.2
>  Environment: Solaris 9 running sun JDK 1.4.2_06
> Windows 2kSP4 running sun JDK 1.4.2_07b5
>     Reporter: Will Lauer
>  Attachments: wsdl.zip
>
> While using java2wsdl and then wsdl2java to generate first WSDL from an 
> interface definition and then proxy stubs from the wsdl, the resulting stubs 
> diff when generated on Solaris vs Windows. Specifically, the arguments to 
> bean constructors may be placed in different orders depending on platform. 
> The prevents the use of common implementation classes being writen to use 
> these generated stubs on all platforms.
> It looks like the problem is with 
> src\org\apache\axis\wsdl\toJava\JavaBeanWriter.java in the method 
> writeMinimalConstructor(). There seems to have been a change between axis 
> 1.2RC3 and axix 1.2 RTM that removed code to sort the constructor arguments.

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

Reply via email to