Web Service WLS9.2 and WLS6.1 SOAP compatibility

Question

We have a Web Service (running on WLS6.1) which has been published for a long time, and many customers have developed their own clients.
Now we must upgrade our Web Service from WLS6.1 to WLS9.2. In practice we had to re-develope the Web Service starting form the original WSDL.
The new WSDL is identical to the original one, and the business code inside has obviously been kept the same.
The new Java Test Client that we generated with clientgen (WLS92) works fine, but we need to guarantee total compatibility for all the clients developed for the 6.1 version.
Unfortunately testing our new Web Service (WLS9.2) with our old java Client (developed with WLS6.1), we found that the SOAP implementation of arrays has changed, and therefore the old client is not compatible with the new Web Services.
Is this a known issue? Is there a workaround or a solution to this problem?
== WLS6.1 array "listaPacchetti " SOAP implementation ==
<listaPacchetti xsi:type='SOAP-ENC:Array' xmlns:bean='java:smash.webservices.bean' SOAP-ENC:arrayType='bean:PacchettoBean[2]'>
<item xsi:type='bean:PacchettoBean' xmlns:bean='java:smash.webservices.bean' >
<numeroSmsResidui xsi:type='xsd:int'>2908</numeroSmsResidui>
<flagOnOffNet xsi:type='xsd:int'>1</flagOnOffNet>
<numeroSmsIniziali xsi:type='xsd:int'>4000</numeroSmsIniziali>
<idPacchetto xsi:type='xsd:string'>9693</idPacchetto>
<cessato xsi:type='xsd:int'>0</cessato>
<dataScadenza xsi:type='xsd:string'>28-02-2008</dataScadenza>
</item>
<item xsi:type='bean:PacchettoBean' xmlns:bean='java:smash.webservices.bean' >
<numeroSmsResidui xsi:type='xsd:int'>1866</numeroSmsResidui>
<flagOnOffNet xsi:type='xsd:int'>0</flagOnOffNet>
<numeroSmsIniziali xsi:type='xsd:int'>2000</numeroSmsIniziali>
<idPacchetto xsi:type='xsd:string'>9694
</idPacchetto>
<cessato xsi:type='xsd:int'>0</cessato>
<dataScadenza xsi:type='xsd:string'>28-02-2008</dataScadenza>
</item>
</listaPacchetti>== WLS9.2 array "listaPacchetti " SOAP implementation ==
<listaPacchetti>
<numeroSmsResidui>2908</numeroSmsResidui>
<flagOnOffNet>1</flagOnOffNet>
<numeroSmsIniziali>4000</numeroSmsIniziali>
<idPacchetto>9693</idPacchetto>
<cessato>0</cessato>
<dataScadenza>28-02-2008</dataScadenza>
</listaPacchetti>
<listaPacchetti>
<numeroSmsResidui>1866</numeroSmsResidui>
<flagOnOffNet>0</flagOnOffNet>
<numeroSmsIniziali>2000</numeroSmsIniziali>
<idPacchetto>9694</idPacchetto>
<cessato>0</cessato>
<dataScadenza>28-02-2008</dataScadenza>
</listaPacchetti>Any help will be appreciated!
Thank you
Laura

Answer 1

Hi
Thanks for your reply
I downloaded OC4J 10.1.2.0.2 and ran it as as a standalone server.
I read the blog you linked and made the changes to the web.xml for the webservice. All of which I was able to do using the property palette in jdev 10.1.2.1.0.
I deployed my webservice to my oc4j standalone server and it appeared as a new application. I editied the orion-web.xml for the new application manually.
When I point my browser at the webservice I get the test page which allows me to pass parameters to the webserive. I invoke the webservice (which does a HTTP GET according to the test page) and the webservice runs. No user and password is needed though.
What is the expected behaviour? I was hoping that the webservice wouldn't run until I supplied the admin user name and password
paul