[
https://jira.jboss.org/browse/JBIDE-6725?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick updated JBIDE-6725:
-------------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Assignee: Viacheslav Kabanovich (was: Brian Fitzpatrick)
Fix Version/s: 3.2.x
Component/s: esb
Slava, do you have any idea what's going on here?
I suspect that this will be yet another use case folks are using to migrate chunks of ESB
configurations from one file to another or as a way to upgrade to newer versions.
Talking to David Ward on the ESB team the other day, it shouldn't matter what order
the <providers>, <actions>, and <listeners> tags show up in the XML
file. The only order-dependent bits are the actions themselves, since they're executed
in the order they appear in the config file.
Unordered creation of XML actions and listeners tags leading to
schema validation errors - JBoss ESB Tooling
------------------------------------------------------------------------------------------------------------
Key: JBIDE-6725
URL:
https://jira.jboss.org/browse/JBIDE-6725
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: esb
Affects Versions: 3.0.0.GA
Reporter: Rafael Liu
Assignee: Viacheslav Kabanovich
Priority: Minor
Fix For: 3.2.x
Attachments: esb-editor.png
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
JBoss ESB Tooling doesn't order creation of XML actions and listeners tags, but there
are ordering restriction in jboss-esb.xml.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira