cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andrus Adamchik <>
Subject Re:
Date Fri, 08 Mar 2013 15:27:28 GMT
Yeah. All its methods are static. There's no static inheritance in Java (unlike in say Objective
C, you can't truly redefine a static method). So there's no instance behavior to inherit.
In my mind this is a good reason to not ever want to subclass "Cayenne".

Of course API style often comes down to personal preferences :) 


On Mar 8, 2013, at 4:22 PM, Michael Gentry <> wrote:

> I was just looking at introduced in 3.1 and noticed that it is
> declared to be a final class.  Is there any reason for this?  I can quite
> easily see people wanting to subclass it to add their own utility methods
> which would make it easier for all those utilities to be grouped together
> in one bigger class rather than spread out over several classes (from an
> end-user's perspective of having to deal with different imports to access
> the utilities -- obviously there would still be multiple classes, it would
> just be better hidden).
> Thanks,
> mrg

View raw message