Description Vladislav Iliev 2011-06-14 03:39:11 EDT

Build Identifier: I20110526-1708, version 3.7.0.v20110520-0800-9gF7UHNFFt4cwE-pibLJ7m-mS0OWjdqewtz0110

Working with the WTP server adapter and trying to contribute an extension point I’m observing a strange behavior:

When I say “Run as”->”Run on Server” for a particular servlet I expect to have a sequence of 
2 operations : 
•	publish 
•	server start (in my extension point startBeforePublish="false")
This is OK. The entry point here is org.eclipse.wst.server.core.internal.Server#start(String mode2, final IOperationListener opListener)
that calls the operation above in an asynchronous way. This does not suit me, as I want to start the server only if the publish operation is successful.

I found another method public void synchronousStart(String mode2, IProgressMonitor monitor) throws CoreException;
That would do the required work instead of me, but what is strange to me is that nobody calls this method.
I didn’t find even how to force the server adapter to call it.



Reproducible: Always

Steps to Reproduce:
There is no an easy way to reproduce it, but in general
1.Create web application with a servlet
2.Right click on the servlet, then Run as->Run on Server, specify or create new
server - for example Tomcat
3. Simulate failing publish (that's the tricky part). I simulate it easy in my
server adapter by throwing CoreException in publish operation.

Expected: Once the publish operation fails, the server will not be started.
Actual: The server is continues starting.