Hi,
I agree @NotPersistent is better than @Transient. The term serialization
is already occupied by serialization and both concepts (serialization
and persistence) are orthogonal.
Are we still looking for a name for a new annotation replacing both
@Field or @Property or did @Persistent win the race?
How about @Member?
Regards Michael
Hi Andy,
On Jul 18, 2007, at 11:36 PM, Andy Jefferson wrote:
Have I ever told you how much I *hate* using @Transient to describe
@NotPersistent? Transient is a serialization concept and I have no
trouble with a field that is both transient and persistent. That is,
not serialized but stored in the database. So calling something
@Transient is a big ugly blotch. Because if it's really transient,
you should mark it in the class as transient.
No. You never told me ;-) nor did anybody else object when those
annotations
were added a longggg time ago.
So why not @NotPersistent ?
Sounds good. I'll take a closer look at using @Persistent and see if
everything can be made consistent.
Thanks,
Craig
--
Andy (Java Persistent Objects - http://www.jpox.org)
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
[EMAIL PROTECTED] Engineering GmbH Tel.: +49/(0)30/235 520-33
Buelowstr. 66 Fax.: +49/(0)30/217 520-12
10783 Berlin mailto:[EMAIL PROTECTED]
Geschaeftsfuehrung: Anna-Kristin Proefrock
Sitz Berlin, Amtsgericht Charlottenburg, HRB 564 52
