[
https://issues.jboss.org/browse/WFLY-3445?page=com.atlassian.jira.plugin....
]
Paul Ferraro updated WFLY-3445:
-------------------------------
Description:
Currently, protocols must reside within the org.jgroups.protocols package or a within a
subpackage.
I should be able to define a protocol as:
<protocol type="org.foo.MyProtocol" module="my.module"/>
The module attribute should indicate the module in which to locate the protocol class and
should default to "org.jgroups".
was:
I should be able to define a protocol as:
<protocol type="org.foo.MyProtocol" module="my.module"/>
The module attribute should indicate the module in which to locate the protocol class and
should default to "org.jgroups".
Allow custom protocol types in jgroups stack
--------------------------------------------
Key: WFLY-3445
URL:
https://issues.jboss.org/browse/WFLY-3445
Project: WildFly
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Clustering
Affects Versions: 8.1.0.Final
Reporter: Paul Ferraro
Assignee: Paul Ferraro
Fix For: 9.0.0.Alpha1
Currently, protocols must reside within the org.jgroups.protocols package or a within a
subpackage.
I should be able to define a protocol as:
<protocol type="org.foo.MyProtocol" module="my.module"/>
The module attribute should indicate the module in which to locate the protocol class and
should default to "org.jgroups".
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)