Kathy,
Regarding 113309, based on the stack trace
I don’t think you are running with a clean environment. There is a
reference to facet “web” in the stack that has been renamed to “jst.web”.
Are you perhaps running from a workspace that has changes that are not in the
i-build?
- Konstantin
From:
wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Kathy Chan
Sent: Thursday, October 20, 2005
9:31 PM
To: wtp-dev@xxxxxxxxxxx
Subject: [wtp-dev] Web Services
tooling in this weeks integration build
Hi,
Please
note that there are some Web Services tooling JUnit failure in jst.ws.test with
this week's 1021I 01:53 I-build (the one respin with the fix for 113299). This
is due to the fact that Web services tooling still have not react to some of
the J2EE facet changes this week. Since we are in the process of moving
over to use the project facet API as well, we do not plan to fix these JUnit
failures in the current code base in this week's integration build. This
will be fixed in next week's integration build.
With
the 1021I 01:53 I-build, the 4 Web Services tutorials (bottom-up Web service,
top-down Web service, Web service client and Web Services Explorer) work fine
with the following workarounds:
-
After creating a dynamic Web project, the project is not targetted to a server.
I was not able to use Chuck's suggested workaround to use the
"Add/Remove Project Facet" menu item.... select the
Tomcat runtime, and push "bind" button. The "Add/Remove
Project Facet" did not bring up the pop-up as expected (bugzilla 113309).
I was able to workaround the server targetting classpath problem by
bringing up the Properties on the Web project, select "server" and
then selecting Tomcat as the server target.
-
Before going through the Web Services wizard or Web Services Client wizard, the
user would have to manually create the Web project first. If the Web
project does not exist and the Web Services wizard attempts to create one, the
wizard would run into errors and the resulting Web project does not have the
correct structure. Bugzilla 113310
had been opened.
Regards,
Kathy Chan
Rational Java Web Services, IBM Toronto Lab
D3-354, D3/R8V/8200/MKM, 8200 Warden Avenue, Markham, Ontario, Canada, L6G 1C7
kathy@xxxxxxxxxx, (905) 413-3022, tieline: 969-6038, fax: (905) 413-4920
----- Forwarded by Kathy Chan/Toronto/IBM
on 10/20/2005 11:47 PM -----
Chuck Bridgham <cbridgha@xxxxxxxxxx>
Sent
by: wtp-dev-bounces@xxxxxxxxxxx
10/20/2005 08:05 PM
Please
respond to
"General discussion of project-wide or
architectural issues."
|
|
To
|
wtp-dev@xxxxxxxxxxx
|
cc
|
|
Subject
|
[wtp-dev] J2EE Facet Changes in this weeks
integration build
|
|
WTP J2EE Build status for this weeks I Build.
Facets have been integrated into EJB, J2EE Web, and EAR Project creation -
Using existing wizards. (Including EJB/WEB/EAR Import).
Because some sweeping changes were made in the way projects were identified (Typed)
Some of the other module creation features will not be functioning in
this weeks build
Java Utility jars, EJB Client projects, AppClient, and Connector projects are
not functioning for this weeks build. (These are scheduled for next
week).
Project Runtime targeting is not enabled, and by default projects will be
created without Server containers.
A workaround for this week , is to use the "Add/Remove Project Facet"
menu item.... select the tomcat runtime, and push "bind"
button. The classpath will be updated.
The facet's defined in this weeks build:
jst.java
jst.ejb
jst.web
jst.ear
Next week we will have
jst.java
jst.ejb
jst.web
jst.appclient
jst.connector
jst.ear
In this weeks build, because a migrator has not been provided, previously
created workspace projects will not be functional or recognized by the facet
framework.
Rational J2EE Tooling Team Lead
IBM Software Lab - Research Triangle
Park, NC
Email: cbridgha@xxxxxxxxxx
Phone: 919-254-1848 (T/L: 444)_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev