The complication with backporting is:
1) New config flag == change to mbean interface
2) Change to interface is illegal in a CP, hence have to create a new interface and new
probably a trivial new class that exposes it (I'm too lazy to go beyond a
StandardMBean approach.
3) Don't want to change deploy-hasingleton-service.xml to use this new
class/interface, as that's too big a change for a CP (changing config file could break
people who've already altered it.)
All this is resolvable, it's just extra hassle. And the result is that a fix will be
in the codebase, but to take advantage of it users will have to make manual configuration
changes.
(BTW, users can't set the flag to true for HA-JMS per se. They can set it to true for
the jboss.ha:service=HASingletonDeployer service, which in essence means setting it to
true for the entire deploy-hasingleton directory. If they wanted the behavior only for
HA-JMS and had other deploy-hasingleton content, they'd have to separate the content
into another dir and create a parallel HASingletonController to deploy that dir.)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4030622#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...