XSD Schema - Delayer: Disallow "id" attribute within a Chain [INT-2745]

[spring-operator]

Gunnar Hillert opened INT-2745 and commented

XSD Schema: Currently, within a Chain a Delayer must have an "id" attribute. This is inconsistent with the rest of the framework.

The XSD Schema must be updated - so that a Delayer within a Chain disallows the id attribute.

---

Affects: 2.1.3

Issue Links:

• Add a "name" attribute to the delayer that serves as a mutually exclusive alias to the "id" attribute [INT-2746] #6720 Add a "name" attribute to the delayer that serves as a mutually exclusive alias to the "id" attribute
  ("depends on")
• Improve XSD Schema: Inside a Chain Components cannot have a Poller sub-element [INT-2218] #6200 Improve XSD Schema: Inside a Chain Components cannot have a Poller sub-element
  ("is depended on by")

[spring-operator]

Gunnar Hillert commented

The Delayer in fact uses the Id attribute, even inside of a chain. We should create a mutually exclusive "name"-attribute that serves as an alias to the "id" attribute.

[spring-operator]

Artem Bilan commented

Hi, Gunnar
Nevertheless are you planning to introduce "name" attribute?
It's important because the DelayHandler delays Messages in the MessageGroupStore, so we should provide some robustness groupId for them to allow work rescheduling feature after application restart.

[spring-operator]

Gunnar Hillert commented

Yes - Not changing any functionality at all. Just adding the name attribute (in addition to the Schema refactoring)

[spring-operator]

Gunnar Hillert commented

Just issued PR: #624

[spring-operator]

Gunnar Hillert commented

After some discussion - we will actual allow the ID attribute on elements within a chain. Closed PR.