Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Dali Deployment Scenarios
Revision as of 15:37, 9 January 2007 by Unnamed Poltroon (Talk)
Dali Deployment Scenarios
Java SE
- JPA jars in project classpath
- No JPA jar deployment support
Self contained WAR
- JPA jars on target server classpath
- No JPA jar deployment
- JPA jars manually placed in WEB-INF/lib
- JPA jars in JPA Library, automatically copied to WEB-INF/lib (like JSF)
WAR with PU in utility jar
- JPA jars on target server classpath
- No JPA jar deployment
- JPA jars manually placed in WEB-INF/lib
- Means utility jar will need to have JPA Library on it’s classpath
- JPA jars in JPA Library, automatically copied to WEB-INF/lib (like JSF)
WAR in EAR with utility jar
- JPA jars on target server classpath
- No JPA jar deployment
- JPA jars manually placed in EAR and added to WAR manifest through WTP J2EE Module dependencies
- JPA jars in JPA Library, automatically copied to EAR and added to WAR manifest through WTP J2EE Module dependencies (like JSF)