This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 333197 - Container testing requires multiple DI/Bootstrap application/container-managed EAR(EJB/WAR with SSB)/EAR(WAR only) test applications
Summary: Container testing requires multiple DI/Bootstrap application/container-manage...
Status: NEW
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Eclipselink (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL: http://wiki.eclipse.org/EclipseLink/D...
Whiteboard:
Keywords:
Depends on: 316513
Blocks: 330160
  Show dependency tree
 
Reported: 2010-12-24 11:49 EST by Michael OBrien CLA
Modified: 2022-06-09 10:03 EDT (History)
1 user (show)

See Also:
michael.f.obrien: documentation+

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael OBrien CLA 2010-12-24 11:49:49 EST 
>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)
Comment 1 Eclipse Webmaster CLA 2022-06-09 10:03:00 EDT 
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink