History | Log In     View a printable version of the current page. Get help!  
Issue Details (XML | Word)

Key: JBSEAM-2785
Type: Feature Request Feature Request
Status: Open Open
Priority: Blocker Blocker
Assignee: Unassigned
Reporter: Pete Muir
Votes: 1
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Seam

Redesign PersistenceProvider to provide runtime detectetion of JPA impl in use

Created: 27/Mar/08 02:05 PM   Updated: 08/May/08 12:52 PM
Component/s: Core
Affects Version/s: 2.1.0.A1 , 2.0.1.GA
Fix Version/s: 2.1.0.BETA1

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Related
This issue related:
JBSEAM-1946 seam 2.0's persistence:managed-persis... Major Closed
 


 All   Comments   Work Log   Change History   Subversion Commits      Sort Order:
Jay Balunas [27/Mar/08 02:34 PM]
Notes on possible approaches based emails with Pete and myself:

----------------------------------------------------------------------------
Possibly be a <persistence:provider...> tag that could state two things:

1) "provider-class" - that class of the provider to instantiate

2) "entity-delegate-class" - that would the "isInstanceOf(..)" to use the provider

---------------------------------------------------------------------------
Possibly the EntityManagerProxy, or the ManagedPersistenceContext could hold the matching persistence provider impl and just use it as a field (still might require casting). This would be instead of determining the provider every time the parent PersistenceProvider is called.
-------------------------------------------------------------------------

Joshua Partogi [02/Apr/08 10:10 PM]
Does this open the possibilities for us to use JPA implementation other than Hibernate?

Jay Balunas [02/Apr/08 11:14 PM]
Is is possible to use other JPA providers in 2.0.1.GA. See my comment http://jira.jboss.com/jira/browse/JBSEAM-1946#action_12404066. This jira is about making that easier and more flexible.