Basically there is no all in one process to generate everything like JBoss.NET. The current JBossWS implementation was developed for the sole purpose of conforming to the JSEE 1.4 certification. Due to the state of the standards at that time, and the limited time scheduling, all inclusive tools were not written. The new JBossWS implementation will have an all inclusive set of tools, and will implement the latest standards. This is still in the early development phase.
Also, XDoclet is a dying project which will be replaced with Java 1.5 annotations (and perhaps other tools).
XDoclet has a ws4ee module, but it is a piece of junk. It was never finished as the author stopped development, but he gave it to the xdoclet developers in case they wanted to complete it. Instead, they just slapped it into a release.
The current recommended practice is:
WSDL + jaxrpc-mapping - Use jwsdp 1.5 for both
Service Endpoint Interfaces - Use the ejbdoclet xdoclet module to generate the service endpoint interfaces, or write them by hand.
webservices.xml - Write by hand
jboss.xml - Use an xdoclet merge file if you are using jbossdoclet, or write by hand
It is possible to still automate these things in a build by having ant call wscompile in the jwsdp, and making your own generation modules.