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

[scott.stark@jboss.org]

"alesj" wrote : 
  | We can order - and that's what I did - top deployments that are picked by a current scan cycle of our HDScanner.
  | But if the two deployments from above are picked in two different cycles of HDScanner, -ds.xml being in the 2nd one, it will fail again.
  | 
This will always fail, even with dependencies. With dependencies it will be redeployed when the missing ds does show up.

"alesj" wrote : 
  | Some one is not putting the ejbs into JBossWebMetaData.
  | Since I can see that a WebModule has dependencies from JBWMD in the AbstractWarDeployer.deployWebModule method.
  | 
Only a war which explicitly states its dependencies, or the war deployer scanning other contexts for ejbs can add these. The getDepends() value is explicit dependencies declared in a jboss-web.xml descriptor. There is no magic here.

"alesj" wrote : 
  | Your 'seam annotation deployer' is Seam Scanner, which is triggered from ServletContextListener and by that has no knowledge about MC and JBWMD what so ever.
which is too late to be adding dependencies on other deployments. There could be an integration deployer that uses the seam scanner to identify dependencies. 


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

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