cayenne-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Gentry <>
Date Fri, 08 Mar 2013 13:22:52 GMT
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).



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message