[
http://jira.jboss.com/jira/browse/JGRP-634?page=comments#action_12389584 ]
Bela Ban commented on JGRP-634:
-------------------------------
- I removed the 'config' variable which caches the String config
- The setMultiplexerConfig() methods have duplicate methods with a boolean replace
parameter. When true, when calling setMultiplexerConfig() for stack X, then the existing X
will be overwritten, otherwise not.
- There are also a bunch of additional methods (all exposed through JMX), which allow to
remove a config, and remove (clear) all configs
Ability to add stacks to JChannelFactory
----------------------------------------
Key: JGRP-634
URL:
http://jira.jboss.com/jira/browse/JGRP-634
Project: JGroups
Issue Type: Feature Request
Reporter: Brian Stansberry
Assigned To: Bela Ban
Priority: Minor
Fix For: 2.7, 2.6.1
It would be nice to be able to add additional stacks to an existing JChannelFactory.
Example: an AS deployment that wants to use a specialized channel. The deployment could
package an "added-stacks.xml" file and a -beans.xml file that declares something
like this:
<bean>
<!-- Add our stacks to the app server's standard JChannelFactory -->
<install bean="JChannelFactory"
method="addMultiplexerConfig">
<parameter>added-stacks.xml</parameter>
</install>
</bean>
Other services in the deployment would then be able to use some custom stack declared in
added-stacks.xml.
The nice thing about this is it allows packaging of custom stacks with the deployment
that uses them, rather than forcing an edit of a global stacks.xml file.
A quick look at JChannelFactory tells me this should be pretty simple to do. The
existing setMultiplexerConfig methods seem to work like "add" methods, i.e. they
could be invoked multiple times with different passed in values. A minor exception is
setMultiplexerConfig(String) which also caches the passed String in an instance field. So,
it should be simple to add addMultiplexerConfig methods that basically invoke the same
logic.
They should probably be added to the jmx.JChannelFactory as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira