"pedrosalazar" wrote : It's obvious that the alternative 1) is more simpler than number 2). So, when does the alternative 2) makes sense to use?
I am not sure that alternative 2 is really that much harder to "implement" (once you know what files to change), but it does mean that you have to specify the partition name for your clustered EJBs in their jboss.xml descriptor as well since they will use "DefaultPartition" for the partition name if one is not specified. It would be nice if this "default" could be set as well so that the assumed partition name would be what we set the partition name to be upon startup, but that is another topic... For us, alternative 2 made sense because if you change the multicast IP/port, you have to keep up with that information so you do not have two configurations clobbering each other. It is true that you have to keep up with the various partition names (as opposed to ip/port information) with this alternative, but we already had a mechanism that could do that (our clusters already have a naming convention). In the future, we may use both methods in order to get the best configuration across all of our clusters. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3839993#3839993 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3839993 ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
