Jump to: navigation, search

Dali Deployment Scenarios

Revision as of 16:24, 9 January 2007 by Shaun.smith.oracle.com (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Dali Deployment Scenarios

Java SE

  • No JPA jar deployment support
  1. Manually include JPA jars in project classpath
  2. JPA jars in JPA Libary (like JSF)*

Self contained WAR--Single Eclipse Project

  1. JPA jars on target server classpath
    • No JPA jar deployment
  2. JPA jars manually placed in WEB-INF/lib
  3. JPA jars in JPA Library, automatically copied to WEB-INF/lib (like JSF)*

WAR with PU in utility jar--Multiple Eclipse Projects

  1. JPA jars on target server classpath
    • No JPA jar deployment
  2. JPA jars manually placed in WEB-INF/lib
    • Means utility jar will need to have JPA Library on it’s classpath
  3. JPA jars in JPA Library, automatically copied to WEB-INF/lib (like JSF)*
    • Means utility jar will need to have JPA Library on it’s classpath

WAR in EAR with/without utility jar

  1. JPA jars on target server classpath
    • No JPA jar deployment
  2. JPA jars manually placed in EAR and added to WAR manifest through WTP J2EE Module dependencies
  3. JPA jars in JPA Library, automatically copied to EAR and added to WAR manifest (similar to JSF)*


* Not Implemented in 0.5