[
https://issues.jboss.org/browse/WFLY-4194?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated WFLY-4194:
-------------------------------
Description:
The original purpose of the default-stack attribute was to provide a default
ChannelFactory implementation. However, with the introduction of fork channels, there are
now 2 candidate for a default ChannelFactory:
1. The JChannelFactory of the default stack.
2. The ForkChannelFactory of the default channel.
#2 is the better option - and is what Infinispan transports use by default.
This would require that the stack attribute of a channel is required (currently, it is
optional and defaults to the default-stack).
was:
The original purpose of the default-stack attribute was to provide a default
ChannelFactory implementation. However, with the introduction of fork channels, there are
now 2 candidate for a default ChannelFactory:
1. The JChannelFactory of the default stack.
2. The ForkChannelFactory of the default channel.
#2 is the better option - and is what Infinispan transports use by default.
Deprecate default-stack JGroups subsystem attribute
---------------------------------------------------
Key: WFLY-4194
URL:
https://issues.jboss.org/browse/WFLY-4194
Project: WildFly
Issue Type: Enhancement
Components: Clustering
Affects Versions: 9.0.0.Alpha1
Reporter: Paul Ferraro
Assignee: Paul Ferraro
The original purpose of the default-stack attribute was to provide a default
ChannelFactory implementation. However, with the introduction of fork channels, there are
now 2 candidate for a default ChannelFactory:
1. The JChannelFactory of the default stack.
2. The ForkChannelFactory of the default channel.
#2 is the better option - and is what Infinispan transports use by default.
This would require that the stack attribute of a channel is required (currently, it is
optional and defaults to the default-stack).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)