Tom Jenkinson commented on JBTM-1051:
I would add that I believe this issue can be (not formally, but effectively) resolved
Who ever makes a change to src/main/resources/standalone/configuration/*xml should be made
aware that they should also update src/main/resources/docs/examples/config/*xml
This issue should affect:
So I see it as broader than XTS.
That said, +1 on checking whether the testsuite can detect it, but I don't know if the
other configs are tested during testsuite.
Detect when standalone-xts.xml falls out of sync
Project: JBoss Transaction Manager
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Paul Robinson
Assignee: Paul Robinson
Fix For: 5.0.0.M2
We've been having a problem with updates being made to standalone-full.xml and not
being applied to standalone-xts.xml. Most of the time this causes no obvious problem to
us, but clearly will cause a problem for our users. If they try to use XTS in conjunction
with some other technology, such as JMS, that requires a change to the server config, they
will hit problems. However, other times this problem is more obvious as it can prevent the
AS from booting or produce errors.
In the long term, we aim to have a better solution to this multiple server config issue.
In the short term we need to detect when these files fall out of sync and then create a
pull request to fix it.
On failure of the job, we can then fix it manually by:
# Overwriting standalone-xts.xml with standalone-full.xml.
# Adding the '<extension module="org.jboss.as.xts"/>' line back
# Adding the '<subsystem xmlns="urn:jboss:domain:xts:1.0">' block
# Jira the problem in the AS7 jira project and name the issue "standalone-xts.xml
fallen out of sync with standalone-full.xml" (Essential for demonstrating to the AS7
team that this is a problem)
# Create a pull request to resolve the issue.
We need an automated way of detecting this problem, so that it can be fixed ASAP.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
For more information on JIRA, see: http://www.atlassian.com/software/jira