[
https://jira.jboss.org/browse/JBAS-8414?page=com.atlassian.jira.plugin.sy...
]
Jason Greene commented on JBAS-8414:
------------------------------------
IMO we should do this as part of the build, to make sure our examples and extras are
acurate, and allow it to optionally be enabled at boot. However, the default should really
be off since we have some validation ourselves, and editing the xml outside of the CLI and
tooling is a more advanced case that a user could (should) use a schema validating
editor.
Enable schema validation in development
---------------------------------------
Key: JBAS-8414
URL:
https://jira.jboss.org/browse/JBAS-8414
Project: JBoss Application Server
Issue Type: Task
Security Level: Public(Everyone can see)
Components: XML services
Reporter: Thomas Diesler
Fix For: 7.0.0.M1
The server configuration that we ship (i.e. standalone.xml) should be in sync with the
schemas that it references
If there is no automated schema validation chances are high that the xml configuration is
not in sync with the respective
subsystem schemas, which should be the input for tooling I suppose.
--
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