Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338709

Summary:	EJB3.1: Verify JTA 1.1 and JPA 2.0 container managed persistence in Java EE 6 WebProfile stacks
Product:	z_Archived	Reporter:	Michael OBrien <michael.f.obrien>
Component:	Eclipselink	Assignee:	Michael OBrien <michael.f.obrien>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	eclipselink.orm-inbox, peter.krogh
Version:	unspecified	Flags:	michael.f.obrien: documentation+
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:	338837
Bug Blocks:	338708

Description Michael OBrien

2011-03-02 12:47:38 EST

>JEE6 WebProfile adds support for several API's in the web container that traditionally required an ejb container.
- In addition to JPA 2.0 being available as an SE persistence context (RESOURCE_LOCAL) in JEE5, we can now function as a JTA container managed JPA 2.0 persistence context in the web container via JEE6 WebProfile (one profile of many)
>Available in the EJB and WAR container
JSR 317: Java Persistence API 2.0  
http://www.jcp.org/en/jsr/detail?id=317

>The following API's that in JEE5 were only available via the EJB container are now supported in WebProfile
- We need to see how we function (in particular as a JTA application) in a stack utilizing these API's

JSR 299: Contexts and Dependency Injection for the Java EE Platform 1.0
http://jcp.org/en/jsr/detail?id=299
JSR 330: Dependency Injection for Java
http://jcp.org/en/jsr/detail?id=330
JSR 318: Enterprise JavaBeans 3.1 (EJB Lite)
http://jcp.org/en/jsr/detail?id=318
JSR 250: Common Annotations for the Java Platform 1.1 
http://www.jcp.org/en/jsr/detail?id=250
JSR 907: Java Transaction API (JTA) 1.1 
http://www.jcp.org/en/jsr/detail?id=907
JSR 303: Bean Validation 1.0 
http://jcp.org/en/jsr/detail?id=303

Comment 1 Michael OBrien

2011-03-02 13:03:23 EST

11819710

Comment 2 Michael OBrien

2011-03-02 16:47:34 EST

>Verify entity search for Web Profile predeploy acts like EE or SE in the WAR
- do we need to define entity classes in persistence.xml like the following - which for Java EE 5 on the EJB container - we do not.

<persistence-unit name="CollatzGF-ejbPU" transaction-type="JTA">
<class>org.eclipse.persistence.example.distributed.collatz.model.UnitOfWork</class>
<exclude-unlisted-classes>false</exclude-unlisted-classes>

Comment 3 Michael OBrien

2011-03-03 12:50:59 EST

>Verified we have an issue in bug# 338837 for persistence.xml unspecified entities we attempt to use via Criteria or Metamodel when running a Java SE or RESOURCE_LOCAL persistence context

The workaround has been proven to be either of the following
- Global to all entities
        <exclude-unlisted-classes>false</exclude-unlisted-classes>
- Specific to 1+ entities
        <class>entity.Category</class>

Comment 4 Peter Krogh

2011-06-20 14:29:54 EDT

bug scrub

Comment 5 Eclipse Webmaster

2022-06-09 10:03:47 EDT

The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink