On Oct 8, 2009, at 7:09 PM, Michael Gentry wrote:
Does it make sense to use <Persistent> here? After all,
deleteObject() doesn't use it:
void deleteObject(Object object) throws DeleteDenyException;
Good question... Using Object instead of Persistent was a move towards
POJO persistent objects, which only happened half way in 3.0... I am
ok if we do not parameterize the collection here.
Also, I noticed this added to 3.0:
void prepareForAccess(Persistent object, String property, boolean
lazyFaulting);
Seems like that boolean would be another good place to have an enum
instead?
Actually no. To me it looks like a case when boolean is just that - a
boolean.
Andrus
