> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of David > Jencks > Sent: Tuesday, November 13, 2001 9:03 AM > To: Sacha Labourey > Cc: Bill Burke; David Jencks; Andreas Schaefer; > [EMAIL PROTECTED] > Subject: Re: [JBoss-dev] RE: Deployment exception on Clustering > > > Does this mean that the dependencies can go like this? > > > <mbean code="org.jboss.ha.framework.server.ClusterPartition" > name="JBOSS-SYSTEM:service=DefaultPartition"> > </mbean> > > <mbean code="org.jboss.ha.hasessionstate.server.HASessionStateService" > name="JBOSS-SYSTEM:service=HASessionState"> > <mbean-ref>JBOSS-SYSTEM:service=DefaultPartition</mbean-ref> > </mbean> > > > <mbean code="org.jboss.ha.jndi.HANamingService" > name="JBOSS-SYSTEM:service=HAJNDI"> > <mbean-ref>JBOSS-SYSTEM:service=DefaultPartition</mbean-ref> > </mbean> > > > rather than like this: > > > <mbean code="org.jboss.ha.framework.server.ClusterPartition" > name="JBOSS-SYSTEM:service=DefaultPartition"> > <mbean-ref-list name="SynchronizedMBeans"> > > <mbean-ref-list-element>JBOSS-SYSTEM:service=HASessionState</mbean > -ref-list-element> > > <mbean-ref-list-element>JBOSS-SYSTEM:service=HAJNDI</mbean-ref-lis > t-element> > </mbean-ref-list> > </mbean> > > <mbean code="org.jboss.ha.hasessionstate.server.HASessionStateService" > name="JBOSS-SYSTEM:service=HASessionState"> > </mbean> > > > <mbean code="org.jboss.ha.jndi.HANamingService" > name="JBOSS-SYSTEM:service=HAJNDI"> > </mbean> > > ? > > How soon? Would you like a fix for the current situation based on the > second example which is more or less how the system works now (I think I > have such a fix nearly working, but it's always hard to know what "nearly" > means) or is it ok to wait for the first method based on possible > JavaGroups changes? >
No, we cannot wait for JavaGroups changes. This needs to work. Please do not modify the code yourself. I'll do the work, just point me to an example of how I can access the mbean-ref-list. BTW, with the mbean-ref-list example can you please describe to me how calls are ordered? What MBeans get created first? What order does start() get called? <flame> BTW, nobody has explained to me yet WHY YOU ARE REMOVING INIT. All your suggestions are just hacks and will muddy the design and complicate it. Honestly, I'm extremely annoyed that I have to go back to code that had worked before just because somebody doesn't like init(). Could somebody please explain why removing init() is so important and how it is such a critical thing for the JMX framework? </flame> Bill > Thanks > david jencks > > > On 2001.11.13 03:23:23 -0500 Sacha Labourey wrote: > > Hello, > > > > > Unfortunately at this moment in time it is not possible to > hot-deploy a > > > clustered service that depends on state-transfer. You can hot-deploy > > > clustered EJBs though, well at least for SLSB and EBs. Sacha, what > > about > > > SFSBs? > > > > Yes, it is possible. > > > > Next step on my todo list is to speak with Bela about how to implement > > clean > > "local" state transfer and merge protocols. Once done, this should solve > > our > > problems. > > > > BTW Bill, have you seen that JG 1.0 is out with some bug fixes and new > > features (such as merge2 protocol layer) > > > > cheers, > > > > > > > > Sacha > > > > > > > > _______________________________________________ > 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
