geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (GERONIMO-47) Preview of Validator
Date Sun, 31 Aug 2003 05:13:10 GMT
The following issue has been updated:

    Updater: Aaron Mulder (
       Date: Sun, 31 Aug 2003 12:11 AM
             Attachment changed to
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: GERONIMO-47
    Summary: Preview of Validator
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
  Remaining: Unknown

    Project: Apache Geronimo

   Reporter: Aaron Mulder

    Created: Sun, 31 Aug 2003 12:10 AM
    Updated: Sun, 31 Aug 2003 12:11 AM

NOTE: this code shouldn't be committed yet, as we need to pick an XML tool first (it currently
works against XMLBeans, which is commented out of the build).

This is a start on a validator tool.  It is meant to work kind of like JUnit, in that you
write a bunch of test methods in one or more test classes.  The validator base class knows
how to reflect on the test class and run all the methods that start with "test", manage the
validation status code (success, warning, error, etc.) and so on.  Each test class can declare
a DTD XPath of interest (like /ejb-jar/enterprise-beans/session to match session beans) and
will get called once for each "hit" with an argument matching the DD node that matched.

Right now the base code is in o.a.g.validator and there's a quick sample showing what the
test class looks like in o.a.g.validator.ejb.SessionBeanTests

My intention is that the tests use some kind of code for their messages and we read that out
of a resource bundle.  I haven't implemented the actual lookup yet, but the infrastructure
is there.  I'm still not decided on whether the codes should look like "ejb.home.not.public"
or "ejb." or what.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message