[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-1264: ------------------------------ Description: 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. was: 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 7. Forum Reference: http://community.jboss.org/thread/169301 (was: http://community.jboss.org/thread/169301) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Erhard Siegl commented on AS7-1264: ----------------------------------- As I understand it, the standalone.xml do reference the schema (indirecty): <server xmlns="urn:jboss:domain:1.0"> The schema files (jboss-as-config_1_0.xsd) are in docs/schema. You can load these schemas e.g. in Eclipse and it will validate the standalone.xml (and you will find problems in schema and generated configurations) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Erhard Siegl commented on AS7-1264: ----------------------------------- In Eclipse you can use Preferences->XML->Catalog->Add See also: http://mihail.stoynov.com/2009/10/08/how-to-make-eclipse-validate-xsl-and... Then you can tell Eclipse to validate XML-files with a build: Project-Properties->Validation. See also: http://www.eclipse.org/webtools/community/tutorials/XMLValidation/XMLVali... Adding all schemas that way takes a bit of time, but it works and I think its worth it. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Brian Stansberry reassigned AS7-1264: ------------------------------------- Assignee: (was: Brian Stansberry) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka commented on AS7-1264: ----------------------------------- I vote for adding web hint for the sake of easier editing in IDEs. Having it while offline doesn't hurt. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1264?page=com.atlassian.jira.plugin.s... ] Ondrej Zizka updated AS7-1264: ------------------------------ Description: 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/ was: 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. Forum Reference: http://community.jboss.org/thread/169301 (was: http://community.jboss.org/thread/169301) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira