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

[alesj]

"scott.stark at jboss.org" wrote : What we talked about was to order war deployment contexts after all others in the deployment using the relative order as an implicit dependency.
  | 
Sure, if both -ds.xml and .war are in the same deployment.
But usually they are in two separate deployments.

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.

"scott.stark at jboss.org" wrote : If a war starts after an ejb deployment which depends on a ds, the war is also started after the ds.
  | 
That's not the case here.
Probably since there are no ejbs dependencies on the .war.
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.

Basically that's the whole problem, we need to see why those dependencies are not in place.
The relative order from above has no meaning if this is done as it should be.

"scott.stark at jboss.org" wrote : 
  | Seems like a seam annotation deployer is needed to pull these dependencies into the JBossWebMetaData.
  | 
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.

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

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