Ideally the various j2ee api jars would be redistributable, and could be made available by the WTP facet implementations. Currently, we either need some "runtime" that acts as a classpath provider, or the user has to manually enter a path to the jars. The "jst.web" facet implementation provides an example.
And yes, EJB 3.0 is going to fun because it messes with the traditional notion of "EJB projects" having to be exclusive to "Web projects". If all goes well, I expect that there will be an ejb 3.0 facet available in the WTP 1.5 web project wizard... -Ted -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Shaun Smith Sent: Tuesday, October 25, 2005 11:54 AM To: General discussion of project-wide or architectural issues. Cc: [EMAIL PROTECTED] Subject: RE: [wtp-dev] Meeting to discuss Project Facet UI integration ... Recommendations: ... 4) First page: option to select a Runtime instance * Note that for a web project, selection of a runtime will be required for the Finish button to enable. If a user does NOT select a runtime on the first panel, then he will be required to continue through to the facet pages in order to set up classpath for the servlet api jar(s). Is there a similar requirement for setting up ejb classpath? Tim, For the upcoming EJB 3.0 Entity support in Dali we have the option of deploying out of container so sometimes we're going to want to not choose a runtime but instead setup the classpath just like you describe for the servlet api jars. We've just been talking about how to configure the classpath to handle the in container and out of container deployment scenarios. Sounds like the facet framework will make this easier for us. Shaun www.ecilpse.org/dali _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
