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

[alesj]

"pete.muir at jboss.org" wrote : 
  | Note, the deployment order is different if you deploy to the already running app server.
What do you mean by deployment order?

Here is my analysis of the problem:
anonymous wrote : 
  | Indexer EJB depends on persistence.units:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,unitName=dvdDatabase
  | 
  | persistence.units:ear=jboss-seam-dvd.ear,jar=jboss-seam-dvd.jar,unitName=dvdDatabase depends on jboss.jca:name=dvdDatasource,service=DataSourceBinding
  | 
  | jboss.jca:name=dvdDatasource,service=DataSourceBinding is picked up by RARDeployer which creates matching ServiceMetaData
  | 
  | TomcatDeployer also creates ServiceMetaData
  | And it's TomcatDeployer that deploys/starts Seam applications (for those unfamiliar with Seam).
  | And in there Indexer EJB is being looked-up in JNDI. Resulting in failure.
  | 
  | So, both TomcatDeployer and RARDeployer, need to be before ServiceDeployer (which deploys ServiceMetaData)
  | 
  | And therefore why Indexer EJB is only fully installed after TomcatDeployer.
  | 
  | I currently don't see how to solve this w/o Seam knowing about the dependency. 

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

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