Brian Stansberry created WFCORE-3315: ---------------------------------------- Summary: Use ordered collections in the transformer description code Key: WFCORE-3315 URL: https://issues.jboss.org/browse/WFCORE-3315 Project: WildFly Core Issue Type: Enhancement Components: Domain Management Reporter: Brian Stansberry Priority: Minor To be decided: as transformation descriptions are built up should we use ordered collections in order to try and retain the original order? I do not want to make retention of order in any way a formal contract of the system, as the complexity and number of data transformations that happen between the subsystem code building up a transformation description and the ultimate application of the transformation make such a contract too difficult to explain and too difficult to test and maintain. But, internally retaining some order may help avoid issues. If subsystem devs naively code things in what seems like a logical order and then that works, great. The con is, there would be no contract here so said subsystem dev may naively code something exotic that happens to work but then gets broken later when some necessary change in the kernel alters the ordering. If the breakage is detected and the exotic transformer can be fixed as part of bringing in the kernel change, then it's not a big deal. But if it's not detected or if the exotic transformation can't be undone, then we'd be stuck. -- This message was sent by Atlassian JIRA (v7.2.3#72005)