Well, currently, the validation rules are all setup like this. They
are very relaxed about spelling errors, the validation will just be
considered as succeeded. Changing this means that it has to become a
hard error (an exception), there are no warnings in RIFE at all
besides one that says when the EngineClassLoader isn't instantiating
elements.
The reason for this is that in time warning become a crutch more than
anything else because people leave them all on during development and
then you spend your time reading through the console output.
Please file an issue about this in Jira and I'll see about making
throwing an exception in case a property isn't present.
On 10 Aug 2006, at 11:45, Erik Bogghed wrote:
Hi,
While setting up validation I encountered the following due to user
error. If the sameAs() is misspelled or
the property is missing the ConstrainedProperty rule is simply
dropped (not added) and the validation
passes. I guess it would be better to notify the developer of the
problem with the missing property.
See below for example of user error :-):
protected void activateValidation() {
...
addGroup("setup")
.addConstraint(new ConstrainedProperty("password2")
.persistent(false)
.notNull(true)
.minLength
(RifeConfig.Authentication.getPasswordMinimumLength())
.maxLength
(RifeConfig.Authentication.getPasswordMaximumLength())
.sameAs(password));
...
}
Erik
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
--
Geert Bevin
Uwyn "Use what you need" - http://uwyn.com
RIFE Java application framework - http://rifers.org
Music and words - http://gbevin.com
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
