| Summary: |
Container testing requires multiple DI/Bootstrap application/container-managed EAR(EJB/WAR with SSB)/EAR(WAR only) test applications |
| Product: |
z_Archived
|
Reporter: |
Michael OBrien <michael.f.obrien> |
| Component: |
Eclipselink | Assignee: |
Project Inbox <eclipselink.foundation-inbox> |
| Status: |
NEW
---
|
QA Contact: |
|
| Severity: |
enhancement
|
|
|
| Priority: |
P3
|
CC: |
eclipselink.foundation-inbox
|
| Version: |
unspecified | Flags: |
michael.f.obrien:
documentation+
|
| Target Milestone: |
--- | |
|
| Hardware: |
PC | |
|
| OS: |
Windows 7 | |
|
| URL: |
http://wiki.eclipse.org/EclipseLink/DesignDocs/316513
|
| Whiteboard: |
|
| Bug Depends on: |
316513
|
|
|
| Bug Blocks: |
330160
|
|
|
>We need a more varied numbers of application framework testing on application servers. As we may be missing some deployment scenarios specific to certain architectures like the following. - container managed / application managed (RESOURCE_LOCAL or JTA) - various (DI) dependency injection @EJB injection on Servlet of @Stateless containing @PersistenceContext EntityManager - @PersistenceUnit injection of EMF on Servlet - @Entity in WAR, EJB.jar or external entities.jar Various EclipseLink library locations - at root of server classpath - in modules - in domain lib - as shared library external EAR - internal to APP-INF/lib in EAR (application managed only or override of server classpath) - internal to WAR lib (application managed only)