[
http://jira.jboss.com/jira/browse/JBSEAM-3028?page=comments#action_12414372 ]
Dan Allen commented on JBSEAM-3028:
-----------------------------------
That's what I'm still trying to figure out. It's possible to share the
persistence context between a JavaBean components, but it doesn't share the same one
that another EJB component would use (if if extended).
Like I said, this is still in the research phase. I just woke up and thought, brilliant!
We can take the same approach with persistence contexts that we do with transaction
synchronization.
add ContainerManagedPersistenceContext
--------------------------------------
Key: JBSEAM-3028
URL:
http://jira.jboss.com/jira/browse/JBSEAM-3028
Project: Seam
Issue Type: Feature Request
Components: Core
Affects Versions: 2.1.0.A1, 2.0.2.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Priority: Minor
Fix For: 2.1.0.GA
Attachments: JBSEAM-3028-v1.txt
Original Estimate: 2 hours
Remaining Estimate: 2 hours
Perhaps this is silly, perhaps not. I have developed a wrapper around a container-managed
persistence manager, avoiding the need to have to lookup the EntityManagerFactory in JNDI.
The main limitation here is that you cannot use this with EJB components, so it is really
just a convenience of configuration if the Java EE application server happens to offer the
ability to create an EntityManager for you. This also only works with the default
persistence unit.
--
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