[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3388) Pages.xml file should be validated against its schema at runtime

Arron Ferguson (JIRA) jira-events at lists.jboss.org
Fri Sep 5 13:45:38 EDT 2008


    [ https://jira.jboss.org/jira/browse/JBSEAM-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12428435#action_12428435 ] 

Arron Ferguson commented on JBSEAM-3388:
----------------------------------------

Add to the docs that the user can add the following Ant task for performing validation checking against the pages.xsd schema:

  <!-- Validate the pages.xml file -->

  <target name="validate-configs" depends="init-build" description="Validate pages.xml file">

    <schemavalidate failonerror="yes" lenient="no" warn="yes" disabledtd="true" fullchecking="true">

      <fileset dir="${config-dir}" includes="pages.xml" />

    </schemavalidate> 

  </target>

This assumes a configuration directory that contains a pages.xml file. Could use this to later validate all xml files (e.g., persistence.xml, components.xml, etc.). Remind the user that this task should happen before compiling ... it's annoying to compile and then come across a validation error that stops the build. :)

> Pages.xml file should be validated against its schema at runtime
> ----------------------------------------------------------------
>
>                 Key: JBSEAM-3388
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3388
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 2.1.0.BETA1
>         Environment: N/A
>            Reporter: Arron Ferguson
>            Assignee: Norman Richards
>            Priority: Minor
>
> The pages.xml file that is used in Seam apps should really be validated when the WAR/package is deployed on the server. This would help alleviate a lot of the false positives (i.e., bug reports that are not due to bugs but are in fact users adding mistakes to the pages.xml file). Additionally Seam team developers would form a tighter contractual binding of what the specs state should happen, with what the API implementation is actually doing. This would most likely result in a reduction in bug reports due to false positives as well as actual bugs.
> To complement this, a blurb in the Seam manual on how to create an Ant task with validation could be added as well as a small sample application for validating pages.xml files with the pages.xsd schema. If I have time later today I'll post to this report a snippet of code for each.
> - Arron

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the seam-issues mailing list