I have an application that is currently out in the wild that uses the Wingfoot 1.02 client library, due to a bug in this version, nested vectors are not processed correctly so I have to manualy take the information out of the incoming respose and parse it into my object... I do this by using the .getValueAt(x) method. It works just fine, except, that version always expects that correct values will be in the same order. I realize that this is a very very bad thing to do, and I have changed it for the next release, however I want to maintain backwards compatibility.
Now the development environment, we are running Jboss/Tomcat4/Apache on Redhat, on my local machine I run Windows Xp and Jboss 3/Tomcat4 both using SOAP 2.3.1. Now whats strange is that on the version that requires the values to be in the same order works fine on my machine, however on our dev server it doesn't... The reason it doesn't work is because even though AFAIK, they are using the same code, when I sniff the packets going accross are in different orders... Therefore it doesn't work with the older versions... I suppose my question is, what determines the order in which they are server side parsed, seen below? Could the difference be some mismatched versions on the server? Thanks for your help Jeremy ------------ >From Dev Server: <item xmlns:ns4="urn:juiced-firewallupdate" xsi:type="ns4:fu"> <IPAddress xsi:type="xsd:string">10.132.138.117</IPAddress> <allowed xsi:type="xsd:boolean">true</allowed> <consumerID xsi:type="xsd:int">743</consumerID> <sessionID xsi:type="xsd:int">2902</sessionID> </item> >From my Machine: <item xmlns:ns4="urn:juiced-firewallupdate" xsi:type="ns4:fu"> <consumerID xsi:type="xsd:int">743</consumerID> <IPAddress xsi:type="xsd:string">10.132.138.117</IPAddress> <sessionID xsi:type="xsd:int">2903</sessionID> <allowed xsi:type="xsd:boolean">true</allowed> </item>
