> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Maplesden
> Sent: Monday, November 12, 2001 6:07 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> From what I can follow of this conversation I think what Bill needs is a
> bunch of mbeans to be initialised before any of them are started i.e.
> mbean1.init();
> mbean2.init();
> mbean3.init();
>
> mbean1.start();
> mbean2.start();
> mbean3.start();
>
Thank you Mr. Maplesden. Exactly.
> as opposed to
> mbean1.init();
> mbean1.start();
>
> mbean2.init();
> mbean2.start();
>
> mbean3.init();
> mbean3.start();
>
> and as long as he has a way to do this (using postRegister to call init or
> whatever) he will be happy.
>
> AFAICS then the questions are
>
> 1) Can we do this for him? if yes then great.
>
Please, Please?
> 2) Is this absolutely neccessary or is there some fancy way he could keep
> track of things and work around his problem? if yes then ok (except maybe
Yes its necessary to avoid a corrupted state-synchronization on
initialization.
> for whoever has to implement the fancy bit). I think however the
> answer to
> this may be no because it sounds like the HAPartition has to
> exist (i.e. be
> initialised) first and then have other mbeans register with it
> before it is
> then started, and the other mbeans can't be started until HAPartition is
> started, is this correct?
>
> If no to both of the above then we have a problem with David J's new
> deployment stuff...
>
Regards,
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
