Have you read http://www.jboss.org/wiki/Wiki.jsp?page=WSRPCClientStepByStep ?
It explains why it is not at all unreasonable to JBoss on the client side. JBossWS is about J2EE compliant web services on the server *and* client side. If you are looking for a standalone (not J2EE compliant) WS client that does not use the WS4EE client programming model, you might need to configure the Call manually. Have a look at the various client side wikis, to get a better idea whether you want to use JBossWS on the client side or not. On the client side, you could of course use any other SOAP stack as well (i.e. jwsdp, axis). Remember there is a fundamental disconnect between the client/server side of a WS. The client should be able to work solely from the information given in the wsdl. jwsdp and axis both have tools to generate all you need from a remote wsdl. If you use JBossWS on the client you still generate the SEI, SI, User types, jaxrpc-mapping.xml from WSDL but not use the jwsdp propriatary stubs and serializers. The wiki expailns that step by step. Good luck View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3868098#3868098 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3868098 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
