On Jan 15, 2007, at 1:53 AM, Steve Wells wrote:
> Is CAY-400 implying a number of pre-defined keys as well as user-
> defined?
> Perhaps having a number of pre-defined sets such as to allow JPA-
> annotations
> could be possible, if that is what anyone would want.
I haven't thought of it in the context of JPA yet, but the idea was
to define ad-hoc properties for 'unexpected' uses (think extensions).
See my other comment below - IMO keys understood by Cayenne core
should be handled as class fields of corresponding metadata objects.
CAY-400 properties on the other hand will be used to build extensions.
I can imagine an independent module built on top of Cayenne core (and
a corresponding Modeler plugin) that uses CAY-400 metadata properties
to introduce its own set of keys. JPA or your validation annotations
can both be the examples of such modules. These keys will be
predefined from the POV of the extension module, not the Cayenne core.
> CAY-400 could also relate to http://issues.apache.org/cayenne/
> browse/CAY-204,
> managing indexes?
Probably not, as index property will have an associated behavior
(DbGenerator must understand it), so "index" will likely be a regular
field of an attribute class.
Andrus
This archive was generated by hypermail 2.0.0 : Mon Jan 15 2007 - 02:28:49 EST