Yes, building a WSR (Web Service Archive) is exactly like building a JAR. Mine generally contain only the "META-INF/web-service.xml" file. I don't put anything special in the MANIFEST.MF, I just let the jar command build one.
The EAR should reference the WSR in it's "META-INF/application.xml" file. An example is: | <?xml version="1.0" encoding="ISO-8859-1"?> | | <application> | <display-name>My WebService</display-name> | | <module> | <ejb>mySoapyBeans.jar</ejb> | </module> | | <module> | <java>mySoapyService.wsr</java> | </module> | | </application> | This should be all you need. When JBoss deploys the EAR, it will deploy your defined EJBs and also the WSR - which will use the web-service.xml to configure the jboss-net adaptation of Axis. Note that I do have problems with hot-deployment if the signature of the web services changes......in that case I take the lazy way out and restart JBoss. I also had this trouble with Axis on a standalone Tomcat 5 installation. As I recall in that case, I had to use the Axis adminclient to undeploy my service and then redeploy......that was about a year ago, so I might not be remembering correctly. If you want, I can put together a more complete example of this. I'm thinking of doing that anyway, including the use of xdoclet with ant to use as a working example for reference at our company. r, Lance View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3844042#3844042 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3844042 ------------------------------------------------------- This SF.Net email is sponsored by OSTG. Have you noticed the changes on Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now, one more big change to announce. We are now OSTG- Open Source Technology Group. Come see the changes on the new OSTG site. www.ostg.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user