[jboss-jira] [JBoss JIRA] Resolved: (JBAS-5190) Wrong ordering of EJB/WAR startup causes Seam dvd example to fail deployment
Ales Justin (JIRA)
jira-events at lists.jboss.org
Thu Jun 12 09:05:09 EDT 2008
[ http://jira.jboss.com/jira/browse/JBAS-5190?page=all ]
Ales Justin resolved JBAS-5190.
-------------------------------
Resolution: Done
I've added DsDeploymentContextComparator, which pushes all -ds.xml files before any else.
Wars are ordered last, since WARStructure (see deployers.xml) sets the highest relative order - hence push war's deployment context to the end.
> Wrong ordering of EJB/WAR startup causes Seam dvd example to fail deployment
> ----------------------------------------------------------------------------
>
> Key: JBAS-5190
> URL: http://jira.jboss.com/jira/browse/JBAS-5190
> Project: JBoss Application Server
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EJB3
> Reporter: Pete Muir
> Assigned To: Ales Justin
> Priority: Blocker
> Fix For: JBossAS-5.0.0.CR1
>
>
> This causes a problem, as Seam uses a ServletListener to boot itself, and can try look up EJB3s using JNDI (as described http://docs.jboss.org/ejb3/app-server/tutorial/jndibinding/jndi.html ).
> This is reproduced by running
> cd jbossas/testsuite
> ./build.sh _jars-seam
> cp output/lib/jboss-seam-dvd* ../build/output/jboss-5.0.0.Beta4/server/default/deploy
> cd ../build/output/jboss-5.0.0.Beta4
> ./bin/run.sh
> You should get a NamingException from Seam, as it fails to look up the EJB3.
> Note, the deployment order is different if you deploy to the already running app server.
--
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 jboss-jira
mailing list