I'm not sure if the namespace should or shouldn't be qualified. Here's the part
of my wsdl corresponding to the function called that threw the above error. It
may be a bug in the client code I'm using, but if its a bug in jboss, I'm
unsure if its with jboss WS or jboss XB.
|
| http://www.
I have a similar issue, but from client to server. I am using JBoss AS 4.0.4GA
with JBoss WS 1.0.2GA and Easy SOAP on the client side. I have a company POJO
that contains an address field. My test service is called HelloWorldService. My
WSDL is strict, rpc literal with one way operations.
|
Thomas,
this is the beginning of the wsdl (via http://localhost:8080/jbossws) :
|
|
|
|
|
|
|
|
|
|
|
|
I don't understand why my client complains about the properties. In my original
posting just replace "urn:mydom
Juergen,
JSR-181 is related to JAXWS and not JAXRPC. The jaxrpc-mapping file only
applies to JAXRPC. The mapping in JAXWS is defined by JAXB annotations on the
payload objects (i.e. your pojo)
We provide JSR-181 functionality for trivial use cases that do not have special
mapping requirements
