| Allowing Java content in Static Web projects [message #725767]
||Thu, 15 September 2011 17:54
| Carl Anderson
Registered: July 2009
In short, we are looking for adopters that rely on the fact that the wst.web facet conflicts with the jst.java facet. We intend to make a behavior change (not an API change, since this is about a facet exclusion... I would treat it as "Protected Non-API Usage"), and as per WTP_API_Policy, we are making a public disclosure of what we intend to do. If any adopters have an opinion on this, can they please comment on bug 353775 ? I also want to clarify that this is *NOT* making the wst.web facet (Static Web projects) have the same functionality as the jst.web facet (Dynamic Web projects). Here is what I wrote in comment #18:
We are not making the Static Web facet anywhere near the same as the Dynamic Web Facet. You still need a Dynamic Web project for: JSPs, Servlets, a classpath container that includes the contents of WEB-INF/lib, a WEB-INF/web.xml, packaging as a WAR, etc.
Also, to satisfy the prerequisites of the WTP API Policy, there is no deprecation possible, no migration path - this is the removal of the constraints on the jst.java facet that forbids it to be used with the wst.web facet. It is an all-or-nothing change. And we have one adopter that is requiring it.
Powered by FUDForum
. Page generated in 0.02022 seconds