I read the mail on the problems with clustering, and I didn't see any thing will help me. Here is what I need for the CMR code:
ejb1.init(); ejb2.init(); ejb3.init(); ejb4.init(); ejb1.start(); ejb2.start(); ejb3.start(); ejb4.start(); but I am getting is: ejb1.init(); ejb1.start(); ejb2.init(); ejb2.start(); ejb3.init(); ejb3.start(); ejb4.init(); ejb4.start(); -dain > -----Original Message----- > From: Dain Sundstrom [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 14, 2001 4:12 PM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] MBean init/start change broke CMR > > > Hi all, > > I think that the merging of init and start has broken the CMR > code. The CMR > code depends on having a complete two-phase startup. In the > phase 1 (init) > all of the relation ships are connected, and in phase 2 (start) these > relationships are used to create the entity tables with fks, relation > tables, and parse ejb-ql queries. I think that merging the > two has changed > the system to call init and then start for each bean instead > of init for > each bean and then start for each bean. > > I wasn't following the discussion about this, because I > didn't think it > applied to the CMR code (and the messages were very long). > I'm going to go > back and read the messages, but if anyone has a suggestion or > can tell me > the resolution, I would appreciate it. > > -dain > > _______________________________________________ > 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
