[jboss-jira] [JBoss JIRA] (WFLY-762) Add schema references to standalone.xml, domain.xml, host.xml

[jaikiran pai (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-762?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12778135#comment-12778135 ] 

jaikiran pai commented on WFLY-762:
-----------------------------------

Each subsystem has its own set of parsers for each version of the schema. Those parsers have the knowledge of what's supported and what's not supported as elements and attributes. Note that this _isn't_ the kind of validation that I think you have in mind. These parsers *do not* read a xsd and then compare the xml. These parsers just have the knowledge of what's supposed to be there for that specific schema version. Take a look at the EJB3 subsystem 2.0 schema version parser for example https://github.com/wildfly/wildfly/blob/master/ejb3/src/main/java/org/jboss/as/ejb3/subsystem/EJB3Subsystem20Parser.java
                
> Add schema references to standalone.xml, domain.xml, host.xml
> -------------------------------------------------------------
>
>                 Key: WFLY-762
>                 URL: https://issues.jboss.org/browse/WFLY-762
>             Project: WildFly
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Gerry Matte
>              Labels: domain, host, standalone, xml, xmlns
>             Fix For: Awaiting Volunteers
>
>
> It appears that users of Jboss 7 will be often modifying these configuration files as they fine tune their server and when they discover how to implement new features.
> It seems quite surprising to me that these files do not have the schema references identified in the file header.  Any good XML editor would use those references to validate changes and new entries and thereby avoid a great deal of frustration for users and those who provide support for forum issues.
> I realise that if jboss validated each xml file when starting up there would be performance penalty that may be unacceptable to many users.  A command-line switch could be used to either turn on xml validation (if the default were that no validation is performed) or conversely to turn off xml validation if the default state was that xml validation was on.
> Personally I favor having a switch that turns off validation - to be used on production servers only.
> If the schema/dtd files were published online and referenced within the configuration xml files, future changes to the schema structure would be "enforced" upon the user community as they attempted to use an out-of-date version when upgrading to a new version of JBoss AS 7.
> http://www.jboss.org/schema/jbossas/

--
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