It is unreasonable to expect that a ws4ee client can download metadata that relate to its own java nature from the endpoint it is talking to.
WS is about interoperability and client/server side are fundamentally disconnected. Your client might be talking to a .NET endpoint, which will have no notion of xml/java mapping. The route to take is, to use a tool like wscompile to generate all the required ws4ee artifacts (including jaxrpc-mapping.xml) from the abstract contract (the wsdl) and package them with your client in a standard way. A portable client cannot get coupled to the java nature of the endpoint. The endpoint is free to change its implementation any time. In short: generate jaxrpc-mapping.xml from wsdl, don't expect the endpoint to provide it View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3884215#3884215 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3884215 ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
