[
https://issues.jboss.org/browse/JGRP-1820?page=com.atlassian.jira.plugin....
]
Dennis Reed commented on JGRP-1820:
-----------------------------------
Two possible fixes:
- Scan for all classes that extend AuthToken and include their properties in the schema.
- Change the config so it's more generic and can fit into a schema (wasn't that
the reason for EAP's custom JGroups config format?)
(A similar issue also affects any custom protocols -- AUTH is just the only shipped
protocol that doesn't match the schema)
XML schema broken for AUTH
--------------------------
Key: JGRP-1820
URL:
https://issues.jboss.org/browse/JGRP-1820
Project: JGroups
Issue Type: Bug
Affects Versions: 3.4.1
Reporter: Dennis Reed
Assignee: Bela Ban
Priority: Minor
The XML schema does not pass validation for AUTH.
AUTH merges in properties for the pluggable auth_class, which are not currently included
in the schema.
For example the fixed_members_value when using FixedMembershipToken is not included in
the schema and fails validation:
<AUTH auth_class="org.jgroups.auth.FixedMembershipToken"
fixed_members_value="localhost/7900">
</AUTH>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira