> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Jencks
> Sent: Friday, December 07, 2001 1:34 PM
> To: [EMAIL PROTECTED]
> Cc: marc fleury; [EMAIL PROTECTED]
> Subject: Re: [JBoss-dev] current mbean structure confusing
>
>
> 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?
Maybe I'm just really braindead here, but in 2.4.x, MBeans listed after the
AutoDeployer(implicit dependency) did not start until the AutoDeployer
finished deploying everything. Why was this behavior changed in 3.0?
This is very very useful. Otherwise, mbeans depending on EJBs and services
deployed by the AutoDeployer will have to list long lists of MBean refs (is
this correct?) which are hard to maintain.
An even better reason for this behavior is the following scenario we had at
Mercantec:
Mercantec's application receives HTTP requests many times per second by
hundreds/thousands of different clients. Jetty should not be able to accept
HTTP requests until JBoss has completely booted up, and this means all
AutoDeployed components. Otherwise, UI sessions could come up with errors
in this time interval (2-3 minutes to load all our beans), or our batched
XML-RPC requests could fail.
The way you guys are talking, I'm going to have to list MBean refs for all
80 of our EJBS and other datasouces and MBean components!!! That's a
nightmare to maintain and just plain ridiculous.
Do you get what I'm saying here?
Other than that, IMHO, it is plain ridiculous to have to explicitly type in
dependencies for all MBeans. It is just too much work and too hard to
maintain for a large application. Having implicit dependencies by MBean
ordering in a file is simple and elegant and easy to understand. Yes,
specifying dependencies explicitly is very useful, but I'm guessing is not
needed for 80% of applications.
Bill
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
