[
https://issues.apache.org/jira/browse/ARTEMIS-4637?focusedWorklogId=903800&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-903800
]
ASF GitHub Bot logged work on ARTEMIS-4637:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 06/Feb/24 09:36
Start Date: 06/Feb/24 09:36
Worklog Time Spent: 10m
Work Description: AntonRoskvist opened a new pull request, #4810:
URL: https://github.com/apache/activemq-artemis/pull/4810
…dges
I hope this change makes sense as it's a little bit outside of my comfort
zone... it's purpose is to fix a minor annoyance of mine and something Ive seen
confuse some other users as well, where moving or adding a configuration
element in the wrong place causes the config to be invalidated.
A side effect of this change is that the cluster property/attribute
`allow-direct-connections-only` in `static-connectors` would pass validation
even on core-bridges... setting this property has no effect on the core-bridges
either way so I'm hoping it's not a cause for concern. I made it that way to
have current configurations validate as before this change instead if adding it
as a separate element within the cluster config or similar. Ideas on how to
make this better if it's an issue are welcome.
Ideally this would apply to all configuration at some point but I believe
that would require moving to xsd version 1.1 which is not scoped in this change.
Issue Time Tracking
-------------------
Worklog Id: (was: 903800)
Remaining Estimate: 0h
Time Spent: 10m
> Allow unordered xml conf elements for clusters and bridges
> ----------------------------------------------------------
>
> Key: ARTEMIS-4637
> URL: https://issues.apache.org/jira/browse/ARTEMIS-4637
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Anton Roskvist
> Priority: Minor
> Time Spent: 10m
> Remaining Estimate: 0h
>
> This allows any order of xml configuration elements within cluster and
> core-bridge config blocks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)