jboss.entity.manager.factory.jndi.name

[pmuir]

"carlo" wrote:
This function doesn't work anymore in the current jpa deployers release:

<property name="jboss.entity.manager.factory.jndi.name"
value="java:/dvdEntityManagerFactory" />

See
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/jbossas/projects/jpa/trunk/deployers/src/main/java/org/jboss/jpa/deployment/PersistenceUnitDeployment.java?view=markup
at the bottom.

For the moment a persistence unit can only be injected.

Any idea when this will be fixed? We can work around this in Seam, but it's nice to have.

[iradix]

I second that, I just tried to get a Seam app up on JBoss 5 CR2 and it failed due to this limitation. Pete, any short term workarounds you can suggest?

[iradix]

Yikes. I just went through the JMX console and it seems like the EntityManagerFactory is nowhere to be found. I guess I could create one based on the SessionFactory, but that seems pretty dirty.

[jaikiran]

Someone seems to have found a workaround here http://www.jboss.com/index.html?module=bb&op=viewtopic&t=142681

P.S: I have zero knowledge about Seam, so i don't know how good that workaround is.

[pmuir]

There is an easy workaround, use:

<persistence:entity-manager-factory name="myPersistenceUnit"/>

<persistence:managed-persistence-context name="entityManager" auto-create="true" entity-manager-factory="#{myPersistenceUnit}"/>

in components.xml

[iradix]

Thanks guys.

Pete, I'm slightly confused here. The documentation talks about using that component to "bootstrap" a persistence unit. Since JBoss is already finding my persistence.xml and creating an EMF, using your method would that happen twice? If not, I would think that using your workaround might be a better solution to outline in the documentation since it doesn't rely on any JBoss specific config parameters....

[pmuir]

Carlo has said this will be fixed for JBoss 5 GA IIRC.

[atamur]

thanks for advice. but when i do that i get:
The chosen transaction strategy requires access to the JTA TransactionManager

seems that <persistence:entity-manager-factory name="myPersistenceUnit"/> is working outside J2EE container ...

[iradix]

I think the trick is to place

<property name="hibernate.transaction.factory_class" value="org.hibernate.transaction.JTATransactionFactory"/>

<property name="hibernate.transaction.manager_lookup_class" value="org.hibernate.transaction.JBossTransactionManagerLookup"/>

within the properties section of the persistence.xml file.

[atamur]

Thanks! But I actually took the "small-hacky-class" approach from the link above: http://atamur.blogspot.com/2008/11/seam-210ga-and-jboss-500cr2.html

[dimitris]

Can you check if this is fixed in AS trunk?

[wolfc]

It's in jboss-jpa-deployers 1.0.0-Beta2, but that one is also causing regression https://jira.jboss.org/jira/browse/JBAS-6165.
I'm in the process of cutting jboss-jpa-deployers 1.0.0-Beta3.

[faithnomore79]

I'm trying to migrate from Jboss 4.2.3.GA to Jboss 5.0.0.GA and having this problem. I already noticed it in the RC2 version and hoped it would have been fixed.
So it does not seem to be fixed in the GA version.

Is there a specific jar in the jboss lib folder that can be replaced to resolve this problem ?

[jaikiran]

"pKoster" wrote:
I'm trying to migrate from Jboss 4.2.3.GA to Jboss 5.0.0.GA and having this problem. I already noticed it in the RC2 version and hoped it would have been fixed.
So it does not seem to be fixed in the GA version.

Is there a specific jar in the jboss lib folder that can be replaced to resolve this problem ?

Could you please open a new thread in our user forum http://www.jboss.com/index.html?module=bb&op=viewforum&f=221 to discuss this? I does work in AS5.0 GA. In your new thread please provide more details about what you are doing, the configurations you are using and the way you are accessing the entitymanager.