I've released version 0.7 of ValidateThis!, my validations framework for ColdFusion objects, on RIAForge. It includes the following changes:
- Introduction of the ValidateThis.cfc service object
- Removal of reliance on Coldspring
- Implementation of the ValidationErrorCollection interface in the Result.cfc object
- Renamed the tables in the demo database
- New QuickStart guide detailing how to use the ValidateThis.cfc service object
The details of each of these items can be found below:
Introduction of the ValidateThis.cfc service object
Previous to this release the only way to make use of the framework was to integrate it into your Business Objects, thereby adding behaviour to them. Although that is still my preferred method of using the framework, a new ValidateThis.cfc service object has been added which will allow a developer to use the framework by simply instantiating a single component. One then invokes methods on that component, rather than on the business objects themselves.
When instantiating the ValidateThis.cfc object, one also must create a structure that includes some parameters required by the framework. The keys in that structure mirror the ValidateThisConfig bean that was introduced in version 0.6. Below is a description of the keys, along with the default value that is used if the key is missing from the struct:
- definitionPath - This is the location of your xml files, one for each Business Object for which you want the framework to generate validations. The default value is "/model/".
- defaultFormName - This is the default form name/id to be used when generating client-side validations. It is provided for convenience as it is easily overridable on a case by case basis. The default value is "frmMain".
- BOValidatorPath - This specifies the path to the BOValidator component, which is the facade to the entire framework. It is possible that advanced users may want to either extend or override that component with their own version, and this entry allows for that. The default value is "BOValidator", and it is rare that one would have to override that value.
Removal of reliance on Coldspring
Previous to this release the internal components of the framework were wired together using Coldspring. To ease integration I chose to do the dependency injection (DI) manually. You can certainly still use Coldspring to integrate VT into your app if you wish, but it is no longer required.
Implementation of the ValidationErrorCollection interface in the Result.cfc object
In order to allow VT to act as a validation plug-in to Model-Glue scaffolding, I implemented the interface for Model-Glue's ValidationErrorCollection into the Result.cfc object.
Renamed the tables in the demo database
I did some cleanup that involved renaming the tables in the database used by the demo applications. So if you download a new version of the framework and demo zip file, you'll need to rerun the SQL setup scripts, or you could just take a look at them and manually rename your tables.
New QuickStart guide detailing how to use the ValidateThis.cfc service object
A new QuickStart guide can be found in the root of the zip file that describes how to get up and running using the new ValidateThis.cfc service object. I will be providing the same information in a blog posting shortly.
As always, if you have any questions or interest in following the progress of VT, I invite you to join the ValidateThis! Google Group.