You will need to make this dependency if you
have sars that contain ejbs.
sars are deployed first.
You can also specify the dependency in
jboss.xml for the ejb.
Well, according to the (getting started) docs, a SAR is deployed inside out, so the EJB is deployed before the mbean. That is why I cannot put the dependency in jboss-service.xml accompaning the mbean.
The jboss_3_0.dtd does not state anything about dependencies. Could you elaborate on this?
I don't understand why JBoss does not resolve the dependency itself. It knows the datasource used by the entity bean from the jaws.xml ...
The deployment order is determined initially
by the top level package.
jmx object name
The dependencies work at the jmx service level.
We currently have no mechanism to make
a dependency based on a jndi element being bound.
I don't quite get it, in the jboss_3_0.dtd (nor 3_2)there is no such element as . Could you explain please? Remember, I am using 3.0.7.
You are correct.
It looks like it was only added to jboss_3_2.dtd
in the 3.2 release.
It will still work in 3.0, I will fix the dtd.