How is the Sun ONE Application Framework different from other J2EE frameworks?
In a survey of J2EE frameworks, both before and after the inception of the Sun ONE Application Framework, it was found that other J2EE frameworks typically do not address the full range of enterprise J2EE developers’ needs. Instead, these frameworks only try to solve limited portions of the broad range of enterprise development needs, and thus come up lacking when used to build large, real-world enterprise Web applications. Perhaps the most common observed failing is the predominant focus on JSP rendering and tag libraries. Apache Struts is possibly the most well-known example of such a framework. Although JSPs are an integral part of any J2EE Web application, and tag libraries are crucial to reduce JSP authoring costs, they cannot be the primary focus of a framework that attempts to minimize developer work while maximizing application maintainability, both of which are critical for real-world enterprise development. For example, any kind of programmatic construct in the JSP is a maint
Related Questions
- The Sun ONE Application Framework has the notion of a display field. This isn like the J2EE Blueprints or other J2EE architectures Ive seen--why not just pull values directly from a helper bean?
- My Application is working great with CrEme, but why is the Graphical interface so different from Sun’s JDK?
- How is the Sun ONE Application Framework different from other J2EE frameworks?
