| WTP proposal feedback: J2EE Standard Tools and EJB [message #23554] |
Sun, 16 May 2004 19:39 |
Eclipse User |
|
|
|
Originally posted by: ed.burnette.REMOVE.THIS.sas.com
The proposal says the JST sub-project will target "J2EE-compliant
application servers" and goes on to mention JSP, Servlets, EJB, and so
forth. Although this makes for a nice bright line on the architecture
diagram I'm not sure it will be such a good idea in practice. That's because
there are two big classes of J2EE developers - the larger class that uses
JSPs and servlets, and the smaller class that uses EJBs.
The JSP/servlet people don't need all the sophisticated support and
complication that EJB brings. They can use good old Tomcat for development,
maybe deploy with Apache/JRun, and don't need support for JBoss, WebLogic,
WebSphere, etc.. They might use some alternative Model-2 type framework but
in general it doesn't add hugely to the complexity of the environment.
True application server support is, in my mind, a higher value, smaller
audience proposition that could conceivably be left entirely to vendors,
including of course open source vendors like JBoss. The proposal recognizes
there are differences between vendors and there is no domiant
implementation. I'd rather see the project's resources and attention spent
on fundamentals like Server management, JSP debugging, and JavaFamily
integration (playing nicely with JDT according to Erich's grand vision).
If EJB support is included anyway then my feedback is to make it an optional
component. A user should be able to easily get the JSP/Servlet support
without EJB. This implies either a separate download with separate projects
(Java Web Tools umbrella, with EJB sub-project), or at the very least
something that takes advantage of Eclipse's activity concept and hides the
more complex functionality unless and until the developer needs it.
--
Ed Burnette, co-author, Eclipse in Action
www.eclipsepowered.org
|
|
|
Powered by
FUDForum. Page generated in 0.02962 seconds
Home