[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-1195) enforce startup dependency of EntityManagerFactory on Ejb

Pete Muir (JIRA) jira-events at lists.jboss.org
Wed Apr 25 15:01:30 EDT 2007

     [ http://jira.jboss.com/jira/browse/JBSEAM-1195?page=all ]

Pete Muir updated JBSEAM-1195:

    Component/s: Core
       Priority: Major  (was: Minor)

We can't do that as org.jboss.seam.core.ejb is only used by the microcontainer (EntityManagerFactory wouldn't start when in the AS for example).  Perhaps we need some sort of conditional dependency - if X is installed, then install Y after X, otherwise just install Y

> enforce startup dependency of EntityManagerFactory on Ejb
> ---------------------------------------------------------
>                 Key: JBSEAM-1195
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1195
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.2.1.GA
>            Reporter: Matt Drees
>         Attachments: ConfigTest.java, MockServletContextReplacement.java, SeamTestReplacement.java
> A war project created by seam gen uses an EntityManagerFactory component.  Integration tests using the Embedded EJB container work because the Ejb component starts before the EMF component, but this is by chance only.  If the EMF component starts before the Ejb component, it fails.  This has been experienced when trying to run a war project on Tomcat.
> I'll attach a test that shows this.
> I believe the solution would be to add "org.jboss.seam.core.ejb" to the depends list of EntityManagerFactory's @Startup annotation.

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


More information about the seam-issues mailing list