The jaxrpc-mapping.xml is not used - full stop.
It is a JSR109 artifact and does not enter the game with JSR181. With JSR181 the required webservice meta data are obtained through annotations.
I have been following the instructions on http://labs.jboss.com/portal/jbossws/user-guide/en/html/endpoints.html on how to deploy an ejb 3.0 as a web service. I have used wstools to generate the client artifacts (jaxrpc-mapping, stub classes, etc). I have got this to work successfully but why is jaxrpc-mapping not needed for JSR-181? Have I missed something? Am I doing this wrong?
ok, thank you Thomas for the help and the very fast reply,
that means, that we cannot create a service from a existing wsdl and give that wsdl to the customer.
That is ok, we can define our services direct in java with annotations and give the resulting wsdl to the customer.
But what about the other wsdl/schema features like constraints (minOccurs...) or default values? Did the come with EE5 compatible webservices and JAXB annontations?
JSR181 is about server side meta data. It does not need jaxrpc-mapping.xml.
A WS client is fundametally disconnected and does not know nor care about the implementation details of the the server side. It relies on the abstract contract defined in wsdl and needs jaxrpc-mapping.xml to map wsdl contructs to the java.
With JSR109 the server also obtains the meta data from wsdl + jaxrpc-mapping.xml
the only contract to the client must be the wsdl without jaxrpc-mapping.xml. Otherwise we run into problems with non-Java clients like .net or Perl.
wsdl is always language agnostic. With WS4EE you need jaxrpc-mapping.xml.
.net or perl need simmilar mapping meta data to map to their language domain