[jboss-dev-forums] [Design of POJO Server] - EJB/War deployer ordering problem

[pete.muir@jboss.org]

Trunk seems to be starting the war before the ejb3s are started.

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.

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123612#4123612

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4123612