LOL. I pick #1 or #3. :-)
#4 isn't an option -- the code's in EAP; it's supported.
#3 seems to be along the lines of the standard policy in EAP; we don't just fix
everything we think of, since the fix could introduce other issues. We are conservative.
Would #1 be that bad? You create ExtendedHASingletonElectionPolicy with the missing
methods from the AS 5 API. If the injected policy implements Extended, you invoke on it
the way AS 5 does. Otherwise it gets used as it is now. In
ExtendedHASingletonElectionPolicy javadoc, any HASingletonElectionPolicy methods that
don't get called anymore should have comments noting that fact.
Don't get me wrong; I can see how it would get messy. #3 is OK.
I know you did a lot of refactoring to tighten things up in trunk, i.e. with
HASingletonElectionPolicyBase; that doesn't need to happen in 4.x, and *shouldn't*
happen if it might break some custom subclass. HASingletonElectionPolicySimple just needs
to work correctly.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4141508#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...