[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1034) Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2

[Carlo de Wolf (JIRA)]

     [ https://jira.jboss.org/browse/EJBTHREE-1034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Carlo de Wolf resolved EJBTHREE-1034.
-------------------------------------

    Resolution: Out of Date


This issue is reported against a version which is no longer maintained,
which means that it will not receive a fix. As a result we are closing
this bug.

If you can reproduce this bug against a currently maintained version of 
JBoss EJB 3 please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

> Port ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java to Branch_4_2
> ------------------------------------------------------------------------------------------
>
>                 Key: EJBTHREE-1034
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1034
>             Project: EJB 3.0
>          Issue Type: Patch
>    Affects Versions: AS 4.2.2.GA
>            Reporter: Frank Langelage
>             Fix For: Branch_4_2
>
>
> Port the changes made on ejb3/src/main/org/jboss/ejb3/enc/DeploymentPersistenceUnitResolver.java in Head to Branch 4.2.
> Using an ear with seperated session and entity beans (different ejb-modules) I got the exception "There is no default persistence nit in this deployment." when using "@PersistenceContext private EntityManager entityManager;" in my Session Bean.
> Using the head version of the source file within my 4.2.2.GA cvs checkout the problem went away.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira