This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "Category:OWASP Content Validation using Java Annotations Project - SHIP Validator 0.3 Release - Roadmap"

From OWASP
Jump to: navigation, search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
'''''Motivation:'''''
+
To get to a first stable release there are still a few things that need to be completed:
  
For this release we wished to add more javadoc, refactor the code to be more readable and add more diagrams to explain the code.  
+
* A full documentation of the framework architecture and a user manual.
 
+
* A bug tracking system
'''''Usage:'''''
+
* An implementation of a summary that can contain custom error messages and that is easy to query. The idea is to generate the summary in XML and use the standard XML tools to query it.
 
+
* More standard annotations
#Add the SHIPValidator.jar to your classpath
 
#Test whether it works by using the following command: <code>java no.uib.ii.ship.validation.test.Webform</code>
 
#Add the code below to your application to use the validator. Note that the Validator can be reused.
 
 
 
 
 
<code>IValidatorFactory vf = new ValidatorFactory(); //Instantiate a validator factory</code>
 
<code>Validator val = vf.getValidator(); // Create a validator</code>
 
<code>ValidationSummary vs = val.validate(w); // validate the annotated object w </code>
 
<code>System.out.println(vs.toString());</code>
 
 
 
 
 
'''''Documentation:'''''
 
 
 
In the folder tex is an article describing the framework which can be used as a first draft of the manual.
 
 
 
'''''Bug in MetaConstraints:'''''
 
 
 
In the work we discovered and fixed a bug in MetaConstraints. This bug was also in the previous two releases, but has been fixed in the downloadable packages.
 

Latest revision as of 09:25, 11 August 2009

To get to a first stable release there are still a few things that need to be completed:

  • A full documentation of the framework architecture and a user manual.
  • A bug tracking system
  • An implementation of a summary that can contain custom error messages and that is easy to query. The idea is to generate the summary in XML and use the standard XML tools to query it.
  • More standard annotations

This category currently contains no pages or media.