Community
Participate
Working Groups
Build ID: I-I20080314073909 Steps To Reproduce: 1. Create 55 server & start 2. Create a Dynamic Web Project targeting server, and a new wsdl file (for example), but do not add to the server yet 3. right click on wsdl file, run on server, get HTTP Status 404 More information: This is a change in behavior from previous Integration build http://download.eclipse.org/webtools/downloads/drops/R3.0/I-I20080306230652-20080306230652/ - wsdl would run just fine on the server without needing to restart. Note that server status changes from "Synchronized" to "Restart" after step 3 above. Workaround is to restart server then wsdl can be run on server. Note also that got no dialog indicating a server restart was required in order to run the wsdl. This problem is blocking a web services scenario outlined in https://bugs.eclipse.org/bugs/show_bug.cgi?id=222681 - after a web service is created by the web service wizard, the server status is restart, and subsequent generation of web service client fails with exceptions when trying to test (i.e. client slider set to "test"). Workaround is similar to that for new project new wsdl, i.e. restart the server first before creating the client.
This should be a severity P2.
This is the same behaviour that WTP had exposed last week. I don't think this is cause of the problem in bug 222681
We only use the problem with Run on Server on WSDL file as an illustration of the problem we run into in the Web services wizard with this week's driver. I think the problem might be intermitten and that's why we sometimes have the problem and sometimes not. If you are seeing the problem with last week's driver as well, it might be a different problem than what we are noticing with this week's Web service wizard. The problem we are most interested to get fix is bug 222681. If we just create a Web service client on a Web project that has not been added to a Tomcat server, click Finish, the StartServerCommand is calling shouldRestart and getting "true" back. We then call, server.synchronousRestart(ILaunchManager.RUN_MODE, monitor) However, even after this call returns and the status is OK, the server was not restarted properly (as can be seen in the server status). Subsequently we run into problem with Web service sample JSP generation as documented in bug 222681. If the user then manually restart the server and go through the Web service client scenario again, then the scenario would be fine.
*** Bug 222681 has been marked as a duplicate of this bug. ***
We were able to isolate the actual cause of bug 222681 to a change in ResourceSetWorkbenchEditSynchronizer in the org.eclipse.wst.common.emfworkbench.integration plugin. The fact that restarting the server manually seems to solve the problem could be because that action triggers certain resource synchronization which would otherwise not take place. I tried reverting org.eclipse.wst.common.emfworkbench.integration and org.eclipse.wst.xml.core to the version in last week's driver (03/06) and the problem with server tooling status showing incorrectly as "restart" status is not there anymore. So we are just using this defect to track the problem with Run on Server does not restart the server properly when ROS is selected on a WSDL file. Lowering severity.
