Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Dali Deployment Scenarios
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--Single Eclipse Project
- 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--Multiple Eclipse Projects
- 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)*
- Means utility jar will need to have JPA Library on it’s classpath
WAR in EAR with/without 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 (similar to JSF)*
* Not Implemented in 0.5