ws4ee-client not bound

[hsutarwala]

I am getting ws4ee-client not bound error when I try to test the WSDOCClientStepByStep tutorial. I believe I am not packaging the deployment artifact correctly.
I would like to know the structure for deployment of a Document Literal WS client. The tutorial does not indicate how the deployment artifact should be packaged. Also what descriptors need to be included on the JBoss AS and in which directory?
All help is appreciated.
Can we add the instructions added to the tutorial Thomas?

[hsutarwala]

Nobody has an answer to this? I doubt. Can somebody from the JBossWS team answer this?

[thomas.diesler]

The samples attached to the wiki should be a good starting point.
http://www.jboss.org/wiki/Wiki.jsp?page=JBossWS

[hsutarwala]

Thanks Tom for pointing me to the tutorials. Well I am following the same examples but "there is no instructions on how to package a WS client" and that is what I am looking for? There are no instructions in the WS client for Doc/literal tutorial.

[jana01]

The samples were really helpfull. So, in my case it is an app client so I packed a jar with application-client.xml and jboss-client.xml in the META-INF.
After deploying I can see the service via JNDI.

[thomas.diesler]

The webservice testsuite also uses tons of application clients.

Lets preach this again: Your fat clients or non trivial cmd line apps should run on JBoss. At its bare minimum this buys you nameing/lookup (JNDI) and managment (JMX). These two every non trivial app would need anyway. On top of that you can deploy preconfigured WS4EE clients and don't have to use ugly DII.

[anil.saldhana]

http://anilsaldhana.blogspot.com/

Look for a simple tutorial I wrote sometime back which gives you the steps to create/deploy a webservice. If you need more info than this, look inside the webservices testsuite. Do some hard work to gain knowledge. ;)