[
http://jira.jboss.com/jira/browse/JBSEAM-1195?page=all ]
Matt Drees updated JBSEAM-1195:
-------------------------------
Attachment: SeamTestReplacement.java
MockServletContextReplacement.java
ConfigTest.java
This test case demonstrates the potential bug by forcing the *EntityManagerFactory
components to be listed first in servletContext.getAttributeNames().
SeamGen a war project, and put these in the test src folder.
By the way, it'd be fantastic if SeamTest.externalContext, servletContext, etc... were
protected instead of private. It'd make it possible to replace the Mock objects
used.
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
Affects Versions: 1.2.1.GA
Reporter: Matt Drees
Priority: Minor
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