The support for enablement _expression_
as shown below has been added to the validator extension point. The facet
filters support added in the validator ext point in addition to natures
did not scale very well and additional requirements from some extended
teams drove the need for the enablement support which scales very well.
This _expression_ support covers all the combinations that the FacetedProjectPropertyTester
provides as this is the tester class that is used under the covers for
property and value strings.
The ejb validator is changed to use
this support instead of facet filters
The facet filters support still exists
and works in the validator ext point even though it is redundant with this
enablement support. The reason it is still supported is for the fact that
we are not supposed to break any internal api also at this point for 1.5.
Validators using facet filters will continue to work as is and the any
validators that need the enablement _expression_ support can migrate.