It's my fault. The docs said one thing, the code another, and the defaulting
was all set up to work well with an older draft of the EJB spec. I think other
people have complained about this stuff and I just didn't understand what they
were trying to say. Ugh.
So, I have rationalized this stuff as follows:
org.jboss.seam.core.init.managedPersistenceContexts em
| em.persistenceUnitJndiName java:/EntityManagerFactories/testDatabase
Means look in "java:/EntityManagerFactories/testDatabase" for the EMF.
org.jboss.seam.core.init.managedPersistenceContexts testDatabase
Means look in "java:/testDatabase" for the EMF.
There is now no longer any support for just specifying the persistenceUnitName
('cos of changes to the EJB3 spec).
The same thing has been done for managed Hibernate sessions.
In CVS.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3919000#3919000
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3919000
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
