The following comment has been added to this issue:
Author: Aaron Mulder
Created: Tue, 2 Sep 2003 12:57 AM
Body:
Please close this issue. There's now working validator code, but it's going in
with the patch with the new EJB JAR bean tree since it's dependent on that.
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=GERONIMO-47
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
Components:
deployment
Assignee:
Reporter: Aaron Mulder
Created: Sun, 31 Aug 2003 12:10 AM
Updated: Sun, 31 Aug 2003 12:11 AM
Description:
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.5.3.2.1" or what.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
