Community
Participate
Working Groups
Testing M5, I created a J2EE 1.4 Web application on Tomcat 5.0.28 and created a Web service from a simple Java class. (RPC Encoded - the default). The server was running. The wizard paused for around 15 seconds (probably because caching was disabled since that is the out-of-the-box setting at present) with the Status message: "Parsing WSDL file ...", and then failed with the following error message: IWAB0489E Error when deploying Web service to Axis runtime axis-admin failed with {http://xml.apache.org/axis/}HTTP (404)/Web1/services/AdminService I suspect this is a timing probably since the axis jars were copied to the running server. Maybe the axis admin code didn't get started fast enough? I then cancelled the wizard, stopped the server, and enabled caching. I tried again, this time with success, however there was around a 5 second delay when the test client app was created with the status message "Copying SOAP ...". I am cc'ing Jeff because of the performance comments.
Hi Rupam, I think we encountered this defect a while back. Can you have a look. Thanks.
Problem still present in 0.7RC3. Note related bug 102117 has target milestone 1.08M.
I've encountered what I suspect is the same bug and can reproduce it consistently in WTP 0.7 (final) using the following steps. Since they're somewhat different from the original bug report, it might help narrow down the cause of the problem. 1. Create a new dynamic web project (multi-module projects turned on). 2. Copy a WSDL file into the project. 3. Generate a Java client proxy from the WSDL file. 4. Generate a skeleton from the WSDL file (specify a different package). At this point, I get the same 404 error as above at the "deploying" step (right after "Parsing WSDL file"). I don't think it's a timing issue, since I can't access the Axis admin service for that app until I restart the server. Incidentally, could somebody clarify what is the "enable caching" workaround mentioned in the original report? Thanks.
I hit this problem again on the 1.0 M9 candidate. Tomcat 5.0.28 was running since I had just created simple HTML and JSP test documents. I then tested the Web service creation function and got the same error "axis-admin failed". BTW the previous commenter asked about caching - the enable caching comment is that we have a caching URI resolver that gets the J2EE XML schemas for web.xml, etc. Caching improves performance and enables disconnected use. The cache is enabled by default now. You can control it via a Preference page: Internet->Cache. Since restarting the server fixes the problem, I suggest we at least improve the error message to include corrective action, e.g. "Try restarting the server."
I believe this is a dup of 102117 and we have this listed in the Known Bug section of milestones affected. *** This bug has been marked as a duplicate of 102117 ***
Seems to be fixed in RC5. Closing.
