My vote would be to also remove a limitation on the object to extend Persistent 
in the Property API. From a quick glance, none of the functionality requires 
it, so this is purely a design decision. Expression class does not imply 
Persistent object anywhere, so I guess Property should not either. 

@Nikita, what do you think?

Andrus


> On Nov 15, 2019, at 1:50 AM, Lon Varscsak <[email protected]> wrote:
> 
> Hey all,
> 
> I use Property-type classes for all sorts of things, usually for Cayenne
> related activities...but sometimes they're really useful on POJOs too.  The
> new Property related classes (like EntityProperty) require the class to be
> a subclass of Persistent.  I can't see where this is actually
> relevant...but I might be missing something.  Any reason we couldn't remove
> this restriction?
> 
> Thanks,
> 
> Lon
> 
> P.S. -- Still wishing these also implemented Serializable :P

Reply via email to