Why does the Red Hat WAF have a persistence layer instead of just using standard EJB? Why is Red Hat reinventing the wheel?
WAF is primarily a framework for building web applications, and Red Hat’s reasoning for its current architectural direction is best summarized by Sun’s own J2EE Blueprints at http://java.sun.com/blueprints/corej2eepatterns/Patterns/DataAccessObject.html. In addition, there are numerous examples that one could concoct where an EJB server (at least initially) could be deemed to be an overkill given the problem being tackled. This is the sledge-hammer-to-crack-a-nut problem. In essence, the J2EE specification does not mandate a 2, 3, or multitier application model, nor realistically could it do so. The point is that it is important to use appropriate tools for a given problem space. Given that the most common usage for WAF deployment is, to use Sun’s term, the “Web-centric application scenario”, Red Hat opted for the “3-tier Web-centric” architecture, in which “[t]he Web container is essentially hosting both presentation and business logic, and it is assumed that JDBC (and connectors in t
Related Questions
- Why does the Red Hat WAF have a persistence layer instead of just using standard EJB? Why is Red Hat reinventing the wheel?
- Why does the Red Hat WAF have a persistence layer? Why doesn it just create the SQL when and where it is needed?
- Does SAP Web AS 6.40 provide any enhancements for EJB CMP beans, beyond the EJB 2.0 standard?
