[
http://jira.jboss.com/jira/browse/JBSEAM-2785?page=comments#action_12405563 ]
Eric Jung commented on JBSEAM-2785:
-----------------------------------
I think I documented this in the wrong JIRA bug. The problem this solves is two-fold:
1. Not being able to use OpenJPA
2. Injecting EntityManger instances into non-EJBs (i.e., @In not @PersistenceContext) on
Websphere. Without the stuff I documented above, EntityManager is always null in non-EJB
components; e.g., Authenticators on Websphere -- for me.
FWIW, I've changed persistence.xml to use OpenJPA, removed hibernate.jar (but not the
other hibernate-related jars), and OpenJPA appears to work in both EJBs and non-EJBs.
I apologize if I've sullied JIRA
Redesign PersistenceProvider to provide runtime detectetion of JPA
impl in use
------------------------------------------------------------------------------
Key: JBSEAM-2785
URL:
http://jira.jboss.com/jira/browse/JBSEAM-2785
Project: JBoss Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1, 2.0.1.GA
Reporter: Pete Muir
Assigned To: Pete Muir
Priority: Blocker
Fix For: 2.1.0.BETA1
Attachments: components.xml, EMFactoryBridge.java, persistence.xml, step1a.png,
step1b.png, step2a-1.png, step2a-2.png, step2b.png, step2c.png, step3.png, step4.png
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira