> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of David
> Jencks
> Sent: Monday, November 12, 2001 10:22 PM
> To: Andreas Schaefer
> Cc: [EMAIL PROTECTED]; Bill Burke; David Jencks
> Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering
>
>
> This won't do any good. If all required beans are present, the order will
> be
>
> create
> configure
> call before start
> start
> call after start
>
> with no opportunity for anything else to happen. Might as well put
> everything in start.
>
> Unfortunately Hirams suggestion of "after server is started" doesn't make
> sense- you never know when the server is completely started, someone is
> always about to add one more mbean.
>
> The only way the cluster stuff ever worked was there was a more or less
> hidden concept of a deployment unit, with a more or less explicit order,
> which could be used to hide dependencies. This only works if the explicit
> dependencies are between mbeans needed for a deployment unit (the depends
> tag from David Maplesden) or between deployment units themselves (my
> original recursive sar deployment scheme). For everything I've tried so
> far, the mbean-ref method is simpler, clearer, and reduces the need for
> fake and implicit dependencies than either of the other two
> methods, or the
> "ordering in deployment unit" method. For instance, in the
> ConnectionFactoryLoader, there was a really fake dependency on the
> RARDeployer, the only use of which was to help the RARDeployer notify the
> ConnectionFactoryLoaders when it deployed a rar. By making the
> RARDeployment mbean, and having the ConnectionFactoryLoader refer to it,
> the extraneous reference is no longer needed, and the actual dependence is
> clearly exposed.
>
>
> I think there must be a hidden ordering dependency in the cluster file.
Again, I have 2 phase initialization. It's kind of my fault that it's not
clear what exactly this 2 phase initialization is. ClusterPartition should
be delegating init(), start() and stop() to HAPartitionImpl instead of the
initialization logic being divided between the 2 classes.
> The Cluster has to apperar before any of the services it manages, right?,
> so it can be called from the init.
>
> Why not make this dependency explicit?
>
The more important question is, How can I get 2 phase initialization with
the current MBean code base now that you've removed init(). Does your patch
you gave me show how to do this?
Bill
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
