Hi,
Just want to let everyone know that we found problem running simple servlet with the 1105_1946 I-driver. When trying to run a simple echo servlet, I'm getting the error:
javax.servlet.ServletException: Wrapper cannot find servlet class echo.EchoServlet or a class it depends on
Defect 115196 turned out to be a more general problem not specific to Web services. Chuck is currently looking into that.
I would suggest adding running a servlet to smoke test if it's not there already. May be server tooling already has that smoke test and just might not have a chance to run it yet since the respined I-build is not available until after 6:00 pm on Friday.
Kathy Chan
Rational Java Web Services, IBM Toronto Lab
D3-354, D3/R8V/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
[EMAIL PROTECTED], (905) 413-3022, tieline: 969-6038, fax: (905) 413-4920
----- Forwarded by Kathy Chan/Toronto/IBM on 11/07/2005 11:35 AM -----
| Kathy Chan/Toronto/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 11/05/2005 12:20 AM
|
|
Hi,
With the 1104_2243 I-driver, the Web services smoke tests that used to work with workaround stated in the forwarded note with the 1104_0542 I-driver does not work anymore. I could no longer run a Web service successfully. I've open a blocker defect 115196 for the ClassNotFoundException during the running of the Web service. Since the Web services component did not drop any code between these two 1104 I-driver, this could be due to new code path being run now that the problem described in defect 114681 and 115068 are fixed. We need to investigate this further to find out the cause of this new problem.
Also, the problem described in defect 114681 (wizard-created Web project could not be added to Tomcat server) is still here with the 1104_2243 I-driver even though the problem with context root not set in the .component file had been fixed with the latest drop made this afternoon by Chuck. So defect 114681 had been re-opened and the user would still need to create the Web project first before going through the Web service wizard in order to add a project to the server.
Regards,
Kathy Chan
Rational Java Web Services, IBM Toronto Lab
D3-354, D3/R8V/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
[EMAIL PROTECTED], (905) 413-3022, tieline: 969-6038, fax: (905) 413-4920
----- Forwarded by Kathy Chan/Toronto/IBM on 11/05/2005 12:06 AM -----
| Kathy Chan/Toronto/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 11/04/2005 11:58 AM
|
|
Hi,
I tested with the 20051104_0542 I-build. The Web services smoke tests passed with the following workarounds:
- Defect 114681 (cannot add wizard-created project to server) - workaround by creating the projects before going through the Web services wizards
- Defect 115068 (JRE classpath not set) - workaround by going to Project properties to set server target to Tomcat.
Last week, we targeted this week to have the code in for having the Web service wizard create Web project (defect 114044). This code was in but not fully functional due to defect 114681. So we still can't lift the workaround to have to create the projects first.
Regards,
Kathy Chan
Rational Java Web Services, IBM Toronto Lab
D3-354, D3/R8V/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
[EMAIL PROTECTED], (905) 413-3022, tieline: 969-6038, fax: (905) 413-4920
----- Forwarded by Kathy Chan/Toronto/IBM on 11/04/2005 11:23 AM -----
| Timothy Deboer/Toronto/[EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED] 11/04/2005 09:33 AM
|
|
Hi,
Chuck found a blocking problem on this build where the classpaths of facetted projects are not configured correctly - either the JRE or the server classpath is missing. I beleive I've found the cause of the problem, and have opened up blocking bug 115068. We'll need to have this investigated and most likely require a fix before declaring the I-build.
Thanks,
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503 (tieline 969)
[EMAIL PROTECTED]
| David M Williams <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 11/03/2005 09:07 PM
|
|
The much anticipated weekly I-build candidate is ready for "sanity check" ...
http://download.eclipse.org/webtools/committers/drops/I-I20051104-200511040112/
Component leads, please consider these failing JUnits as blocking defects.
org.eclipse.jst.ws.tests_6
org.eclipse.wst.common.tests_13
(and/or let us know effects on general functionality, such as if not even worth sanity testing).
Make sure that any CVS releases are only for documented blocking defects until I-build declared.
We'll still attempt a Friday noon declaration, but that appears to be "high risk" (or "tight timing"?) .
But, all "must-hear teams" please report sanity tests results by noon -- everyone, please note
"requests to rebuild" with blocking defect numbers by noon.
[I believe wtp-releng is appropriate mailing list]
Remember: Chuck and Phil offered to do sanity test disconnected (from the internet :)
(And .... Phil ... has volunteered :) to do so on Linux
[please note results/bugs in sanity tests reports]. _______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev_______________________________________________
wtp-dev mailing list
wtp-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________ wtp-dev mailing list wtp-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/wtp-dev
