Web Services JBOSS 4.0.3 to JBOSS 4.0.4 Port Issues

[mandar_raje]

Hi,

I have a couple of web services running on JBOSS 4.0.3SP1. I access these services using stand-alone clients (Java client using AXIS and Perl client using SOAP Lite). Both clients work fine; can invoke methods and get values returned to them including String Arrays.

I deployed the same application in JBOSS 4.0.4GA. Now both clients are having issues - albeit different issues. Here they are:

1. Java client can invoke methods that return Simple Types, but not String Arrays or Complex Types. Here is the error I see on the client:

org.xml.sax.SAXException: Deserializing parameter 'result': could not find deserializer for type {http://vcc.ws.eds.com/types/arrays/java/lang}StringArray
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.client.Call.invoke(Call.java:2470)

2. Perl client cannot invoke any method. Here is the error I see on the client side (the same error appears in JBOSS log as well):

Error: Endpoint {http://vcc.ws.eds.com/}VCCSecurityQueryPort does not contain operation meta data for: {http://148.92.114.81:7070/vcc_security_ws}doesUserExist


Any ideas? I know the web services stack changed from 4.0.3 to 4.0.4 and JBOSS moved away from AXIS. Are these the known issues?

Thanks.

[thomas.diesler]

The question is whether your clients send valid SOAP messages that conform to the abstract contract in WSDL.

If JBossWS cannot process these valid messages or responds with an invalid message, it would be bug.

Note, the axis based stack was a lot less accurate WRT validity of the processed messages.