issue #29 - baby steps for replacing cloning with a ValidationContext.
issue #29 roughly tying all of ValidationManager functionality to
ValidationContext as a precursor to actually using the
ValidationContext to eliminate rule cloning.
issue #29 - Collections members now validated without rule
cloning. Path references are still a hodgepodge because some
adaptations are still relying on pushing the errors objects' nested
path, and on cloning rules and sub rules with that nested path. Oy.
issue #29 - No longer mixing errors object nested path with context's
nested path. Also, discovered and corrected a bug in validating
increasingly nested collections in child rules.
Issue #29 - Validation template execution without rule cloning. Rule
cloning now fully removed.
Updating POM to 0.7.3 for 0.7.3 branch
Removing empty test class, will re-add when there's like, you know,
tests.
Issue #39 - initial implementation; needs gobs more testing.
Namespace support for custom context and context handler definitions.
Still needs testing.
Issue #39 - Integration testing. Also, allowing context handlers to
specify whether or not the context should be enabled during recursive
sub bean validation. Also, organizing the integration test config
files, since they were becoming quite the pile.
Issue #43 - Implemented; needs testing
Issue #44 - Implemented; needs testing
Issue #43 - Adding ValidationGroupContextHandler by default; added
integration testing.
Issue #44 - Supporting contexts anywhere rules can be run; integration
tests
Issue 38 - Quickie transplant of error logging from ValidationManager
into a dedicated ValidationErrorMessageHandler.
Issue #36 - Added scope by which SPEL can dereference the current
object under validation, after nested & template paths are
applied.
Issue #40 - Parameterization of RuleExecutor, aside: clearing
warnings.
Committing partial progress on #42 so I can switch over to #45
Updating 0.7.3 from Master.
Implementation of #42 - Needs testing.
Unit testing for Issue #42
Fix for Issue #46