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. 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? thanks david jencks On 2001.11.12 20:44:39 -0500 Andreas Schaefer wrote: > Hi Geeks > > To keep Davids changes and to make Clustering working I remember a > suggestion long ago to add a method-call to the arguments of a MBean. > > I would suggest the following: > - a <mbean> can contain a <method> attribute > - <method> attribute supports the call of a non-argument method and > the time can be specified (after creation, before start(), after > start()) > - ServiceDeployer call the method at the appropriate time > > This would look like this: > <mbean code="org.jboss.test" name="JBOSS-SYSTEM:name=test> > <attribute name="Test">gugus</attribute> > <method time="AFTER_START">connect</method> > </mbean> > > As long as we reduce the method to non-args methods we should not > have much to deal with. > > Andy > > ----- Original Message ----- > From: "Hiram Chirino" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Monday, November 12, 2001 5:37 PM > Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering > > > > >It looks to me as if > > >"Because of quirkiness of JavaGroups, services cannot ask for > > > > state-synchronization once the Group connection has been > initiated." > > >means exactly that the ClusterPartition HAS to know EXACTLY which > services > > >are using it. If you do this, the mbean-ref-list will give you what > you > > >want. Otherwise, can you explain how these two statements don't > contradict > > >each other? > > > > > >Won't having this complete list let you hot deploy a ClusterPartition? > How > > >would this be different than server start-up? > > >I think explicitly stating the dependencies is a good idea, even if > they > > >are caused by a limitation of JavaGroups. > > > > > >david > > > > > > > This seem like a good idea. What would the XML syntax be for > specifying a > > mbean reference list? > > > > Regards, > > Hiram > > > > _________________________________________________________________ > > Get your FREE download of MSN Explorer at > http://explorer.msn.com/intl.asp > > > > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
