On 2001.12.07 09:47:31 -0500 Bill Burke wrote: > > > On the other hand, we are experiencing the same issue > > > as Bill with the > > > need to invoke our EJB from a MBean as soon as the > > > EJB is > > > deployed/available. > > > > An EJB is soon going to be an MBean so MBean refs will be usable. > > > > So, in the initializer bean, I have to put a MBean ref for every EJB I > use? > What a pain! Why can't MBean deployment be held up until the > AutoDeployer > finishes? So that you could have an MBean with a dependency on the > AutoDeployer, and that would be that?
Having a dependency on the autodeployer won't do you much good, will it? The autodeploy being present doesn't mean any particular package is deployed. All the *service.xml and sars are deployed by the autodeployer at present, except for the one in conf/default I think we need mbeans for each package (application, ejb module, etc) that you can depend on. The deployment stuff I'm working on is based on this, but I am finding it slow going. david jencks > > > > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
