Running webservices prevents clean shutdown ?

Question

We're using OC4J with eclipse and the development team has to go through the pain of restarting the appserver twice each time we stop/start. After fixing the localhost/127.0.0.1 problem (see *1), things worked smoothly until we started developing webservices. I didn't put it together until the following email arrived in my inbox this morning..
Notice how you have to restart OC4J twice since it won’t entirely remove the application the first time?
This is caused by our super sweet JAXP web services. If you don’t really care about deploying those there is an ugly hack to work around this problem – delete the webservices folder (from your disk not SVN) and the PublicAccessServiceBean which really belongs in the web services folder along with it’s test case. In fact if the web services were in a separate project/jar that the developer could optionally deploy we would have a better solution to this problem.
There must be a way to disable the deployment of the webservices in OC4J which would be a much more sane approach to fixing this problem, but it’s not apparent to the casual user as how that would be done.
I've search the forums and haven't been able to find a direct reference to the webservice problem. Anyone have any ideas ?
(*1) shutting down oc4j fails in eclipse

Answer 1

A solution bubbled up.. for future reference-
For those of you encountering the annoying need to restart your OC4J server within eclipse there is an alternative to removing the webservices folder. It’s a bit of a hack but a bit nicer (especially if you have to modify the web services!) It involves modifying the ant script used by eclipse to deploy to oracle. This script is located in your eclipse plugins folder under:
..\org.eclipse.jst.server.generic.oc4j_1.5.0.v200606130315\buildfiles
and it is called oracle.10.1.3.xml.
Open it up and add the target “undeploy.j2ee.module” to the start of the depends attribute of the target “deploy.j2ee.ear”. If you do this the application will always be undeployed before deployment and should correct the web services deployment issue. The modified node should look like…
<target name="deploy.j2ee.ear" depends="undeploy.j2ee.module,check.skip.ear.deploy" unless="skip.deploy">
The only problem with this hack is that the application has to be deployed already before you modify the script because otherwise the undeploy will fail.