All clustered does is point the configuration name to a continer configuration that is the default for clustering.
If you need a new clustered container configuration, then you have to end up specifying the config name in the jboss.xml descriptor and the clustered element at the bean level is really pointless. It seems just as easy to use the config name and not confuse the issue with the clustered tag. The cluster-config element is now supported at the container configuration level and can be overriden at the bean level. I'll check these changes into 3.0 when I'm finished testing. xxxxxxxxxxxxxxxxxxxxxxxx Scott Stark Chief Technology Officer JBoss Group, LLC xxxxxxxxxxxxxxxxxxxxxxxx ----- Original Message ----- From: "Sacha Labourey" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 21, 2002 3:13 AM Subject: RE: [JBoss-dev] Specification of the clustering info at the bean level seems out of synch > It is not a bad idea. Why was it different? We thought it was easier for a > developer to say <clustered>True</clustered> in jboss.xml than to change a > container configuration. > > From the developer standpoint, he wants his bean to be clustered and he > really doesn't care if it requires a new container configuration or not. > Now, if he wants to be clustered AND to change the container configuration, > he needs to change the container configuration aswell (which is then > logical). This is already possible. > > Are you changes just a way to globally override what's already at the bean > level (I haven't seen your changes in CVS-commit ML)? And what about the > cluster-config tag in jboss.xml? ------------------------------------------------------- This sf.net email is sponsored by: OSDN - Tired of that same old cell phone? Get a new here for FREE! https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
