Removing hyrule from core in 3.0

Just an FYI that hyrule is on the core but will be removed and we will
be creating a set of adapters to adapt to any validation framework for
3.1 and the future. So for now, we will remove it,

Is anybody using the validate() method in the ORM Service?

Yes, I am.

Regards,
Andrew Scott
http://www.andyscott.id.au/

Ok, because we are considering NOT adding hyrule into the core since it is another framework and creating adapters around it.

So we might end up removing it for 3.0 and adding a formalized validation approach by 3.1. The validate method was just a POC we added.

Luis F. Majano
President
Ortus Solutions, Corp

ColdBox Platform: http://www.coldbox.org
Linked In: http://www.linkedin.com/pub/3/731/483
Blog: http://www.luismajano.com
IECFUG Manager: http://www.iecfug.com

We use the hyrule component in CB but overwrote the validation routine
in the ORM service (also added a validateAll routine to handle
multiple objects).

There is so little validation code in the baseORMService that it would
be trivial for someone to add it back in. So I'm in favor of removing
it...

Plus, there will only be more people dependent on it by the time 3.1
hits and running into the same issue with the API change.

.brett

Actually I will have to take what I said back, I do the following

ValidationService.cfc

component singleton extends="coldbox.system.orm.hibernate.hyrule.Validator"
{
}

And use it like this
var validationResults = ValidationService.validate(commentEntity);

Regards,
Andrew Scott
http://www.andyscott.id.au/

From: coldbox@googlegroups.com [mailto:coldbox@googlegroups.com] On
Behalf Of Brett
Sent: Thursday, 20 January 2011 9:55 AM
To: ColdBox Platform
Subject: [coldbox:7754] Re: Removing hyrule from core in 3.0

We use the hyrule component in CB but overwrote the validation routine in
the ORM service (also added a validateAll routine to handle multiple
objects).

There is so little validation code in the baseORMService that it would be

trivial

for someone to add it back in. So I'm in favor of removing it...

Plus, there will only be more people dependent on it by the time 3.1 hits

and

running into the same issue with the API change.

.brett

> Ok, because we are considering NOT adding hyrule into the core since
> it is another framework and creating adapters around it.
>
> So we might end up removing it for 3.0 and adding a formalized
> validation approach by 3.1. The validate method was just a POC we

added.