Hi everyone,
currently, the persistence engine requires your POJOs to implement
the Constrained and Validated interface, which can be quite a burden
if you don't extend the CmfValidation or Validation base classes. I
was thus thinking of adding support for declaring all the meta-data
in an external parallel class.
So if your POJO is named like this:
com.mypakkage.ThisPojo
RIFE would look for:
com.mypakkage.ThisPojoMetaData
If this class exists and implements the required interface, it will
be instantiated for each instance of ThisPojo that is inspected for
meta-data.
Sadly this is not as simple as it sounds, since RIFE's validation is
state-full. It has been designed to stick around as a collector for
all validation errors that can appear in any possible layer, until
the errors are explicitly cleared. To make this possible, I should
add a registry (WeakHashMap) that keeps track of each ThisPojo
instance and the associated ThisPojoMetaData instance.
The most logical location to add this would be an additional
Participant. However, since this is such a fundamental core feature,
it seems awkward to require everybody to add this participant
explicitly. It would this always be added by default to the standard
Repository implementation (maybe even to the custom ones). Another
option would be to just have a static map in ConstrainedUtils, but
that feels very dirty.
What do you think of all this? Do you think it is worth the effort?
Any better ideas to preserve the instance and meta-data mapping?
Thanks for you input,
Geert
--
Geert Bevin Uwyn bvba
"Use what you need" Avenue de Scailmont 34
http://www.uwyn.com 7170 Manage, Belgium
gbevin[remove] at uwyn dot com Tel +32 64 84 80 03
PGP Fingerprint : 4E21 6399 CD9E A384 6619 719A C8F4 D40D 309F D6A9
Public PGP key : available at servers pgp.mit.edu, wwwkeys.pgp.net
_______________________________________________
Rife-users mailing list
[email protected]
http://www.uwyn.com/mailman/listinfo/rife-users
