How to restore the original order of xsd: elements in xsd: sequence wrappers when updating websphere?

Question

So there is a project around these parts that is pretty old. It uses Java 1.4 and XFire to create the first web services (I know, I know, best practices ...). In any case, the chapters recently decided that everyone needs Websphere 7 right now!

Upgrading to Websphere 7 has significantly changed WSDL. For example, earlier, if it was an order (maybe not the right XML, but I think you will understand my meaning)

<xsd:sequence> <xsd:element type="xsd:date" name="blah" /> <xsd:element type="xsd:string" name="blah2" /> </xsd:sequence> 

The new order is a place that breaks down old devices that try to use the (functional) service:

 <xsd:sequence> <xsd:element type="xsd:string" name="blah2" /> <xsd:element type="xsd:date" name="blah" /> </xsd:sequence> 

Now, I assumed that they take their old WSDLs and use XFire to simply use static (i.e. not code-generated) WSDLs to deploy for repair.

But is there a way to make Websphere 7 not automatically reorder? This is even a Websphere 7 bug (maybe XFire?)

Answer 1

You cannot change the order, as it is generated by the server. You can modify your Java file in Websphere to match your original wsdl. If I were you, I would generate java files from the original wsdl.