[ https://issues.apache.org/jira/browse/ARTEMIS-3284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Étienne Hossack updated ARTEMIS-3284: ------------------------------------- Summary: Clarify ordering of elements in broadcast group XML configuration (was: Clarify or remove ordering of elements in broadcast group XML configuration) > Clarify ordering of elements in broadcast group XML configuration > ----------------------------------------------------------------- > > Key: ARTEMIS-3284 > URL: https://issues.apache.org/jira/browse/ARTEMIS-3284 > Project: ActiveMQ Artemis > Issue Type: Improvement > Components: Configuration > Reporter: Étienne Hossack > Priority: Minor > > The XSD requires the elements of the {{<broadcast-group>}} tags to be in > order. This is because an {{xsd:sequence}} element is used instead of > {{xsd:all}} > It has been so since the HornetQ donation. {{<discovery-group>}} [is not > ordered|https://github.com/apache/activemq-artemis/blob/f491651fdbc911e11c470afb3c0f7f6da1d74063/artemis-server/src/main/resources/schema/artemis-configuration.xsd#L1371]. > Users may encounter cryptic error messages such as the below if they apply > configuration [as in the > documentation|https://github.com/apache/activemq-artemis/blame/f491651fdbc911e11c470afb3c0f7f6da1d74063/docs/user-manual/en/clusters.md#L153] > There are 2 ways forward: > # Update the documentation, as the current schema is correct. > We assume the current schema is correct because this allows one to have an > unbounded number of {{<connector-ref>}} elements in broadcast groups > # Alter the current schema to allow exactly 1 connector ref, and remove the > ordering constraint. > I do not have sufficient familiarity with the functionality/intent of > broadcast groups to recommend the right approach here, but am happy to take > follow through on either path. -- This message was sent by Atlassian Jira (v8.3.4#803005)