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.
Difference between revisions of "Dali Deployment Scenarios"
m (→Dali Deployment Scenarios) |
m (→Dali Deployment Scenarios) |
||
| Line 2: | Line 2: | ||
'''Java SE''' | '''Java SE''' | ||
| − | |||
* No JPA jar deployment support | * No JPA jar deployment support | ||
| + | # Manually include JPA jars in project classpath | ||
| + | # JPA jars in JPA Libary (like JSF) | ||
'''Self contained WAR''' | '''Self contained WAR''' | ||
# JPA jars on target server classpath | # JPA jars on target server classpath | ||
Revision as of 17:14, 9 January 2007
Dali Deployment Scenarios
Java SE
- No JPA jar deployment support
- Manually include JPA jars in project classpath
- JPA jars in JPA Libary (like JSF)
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)