A J2EE Webservice client needs 4 components
1) WSDL
2) jaxrpc-mapping.xml - to preserve the java & wsdl mapping
3) Java types (SEI + JavaBeans)
4) service-ref tag in whatever your deployment descriptor is

If you are starting development then you will only have 1, and will need to 
generate 2 and 3, and hand code 4.

The following wscompile command will do this for you:
wscompile -keep -import -f:wsi -mapping jaxrpc-mapping.xml config.xml

If your webservice is a document/literal webservice, you can control whether 
wscompile generates a wrapped, or bare service endpoint interface by using 
-f:unwrap, and -f:dontunwrap respectively

Since wscompile expects a plain JAX-RPC client (and not a J2EE client), it 
generates a bunch of sun implementaiton classes (like serializers). The only 
types you need are the plain JavaBeans that represent complex types in your 
wsdl file.

-Jason


View the original post : 
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3914798#3914798

Reply to the post : 
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3914798


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user

Reply via email to