Order of Exceptions in generated classes is non-deterministic

[harrisric]

Where a wsdl operation has multiple faults defined the order in which those appear on the generated classes is not deterministic. This means that generating classes from the same wsdl does not guarantee that they are identical and makes it more difficult to compare for differences between the classes generated from different versions of a wsdl.

It seems that this might be fixed by making com/sun/tools/ws/processor/model/Fault implement comparable and then use TreeSet within that and com/sun/tools/ws/processor/model/Operation when handling faults rather than HashSet.
There is a slight issue that Fault does not have any final properties so an implementation of comparable (e.g. based on name) is not strictly stable, but there seems to be no code that alters name.

[lukasj]

Can you share some WSDL one can use to test this?

[harrisric]

Hi @lukasj - the WSDL that has been problematic for me is this one: ws-client.zip
Unfortunately its quite large.
The problem shows up for example in the generated file AlertNotificationService2016:

[lukasj]

thanks. Problem seems to be in the codemodel library from jaxb where the order of throws in the method signature is maintained but the order of parts of the javadoc comment (throws, params,...) is not