Why does the Red Hat WAF have a persistence layer? Why doesn it just create the SQL when and where it is needed?
A persistence layer has been developed as part of the WAF for the purpose of encapsulating database access routines. This is desirable for at least two reasons: abstraction and database independence. By encompassing the SQL statements in Java objects, the database access routines are developed in a scalable environment. Also, the applications are isolated from the schema changes (which may occur in future versions) since the database access routines are encapsulated by a standard API. The second reason, database independece, is desirable because it means that the Java code can easily be ported from one database to another by changing a small set of centrally located files (as opposed to modifying every file that interacts with the database).
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?
- What is needed to create a village in Antarctica so people could live there permanently?