1.2.0CR3 returns

[juergen.zimmermann]

I tested the new JBossWS 1.2.0CR3 with
a) Eclipse/WTP and the generic "Web Services Explorer"
b) The reference implementation for JAX-WS on the client side.

There is no problem if the web service doesn't need any input parameter and just returns a result, e.g. a string.

However, if the web service's operation needs an input parameter (e.g. a long value) then I get this error message: "Cannot find child element: arg0".

Eclipse's Web Services Explorer shows the following as the submitted SOAP message:

<?xml version="1.0" encoding="UTF-8" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
 <soapenv:Body>
 <ns0:findNachname xmlns:ns0="http://ws.hska.de">
 <long_1>1</long_1>
 </ns0:findNachname>
 </soapenv:Body>
</soapenv:Envelope>

And the following code as the returned SOAP message:

<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
 <env:Header />
 <env:Body>
 <env:Fault>
 <faultcode>env:Server</faultcode>
 <faultstring>Cannot find child element: arg0</faultstring>
 </env:Fault>
 </env:Body>
</env:Envelope>

[juergen.zimmermann]

Instead of the WSDL file generated by "wstools" I used the WSDL file in server\default\tmp\jbossws: Eclipse' Web Services Explorer works fine.

Thus there seems to be any difference between the output of wstools and the WSDL file generated at runtime...

However, using JAX-WS RI for the client still fails.

[juergen.zimmermann]

This following namespace declaration is not generated by wstools

xmlns:ns1='http://jaxb.dev.java.net/array'

After fixing this defect I had no problems in generating a client using JAX-WS RI !!!