Hi Andy,

On Jul 18, 2007, at 1:46 PM, Andy Jefferson wrote:

Hi Craig,

It might be a good time (as we're almost done with this) to replace
@Field and @Property with @Persistent. That would make it easier to
describe that either a field or property is being described.

While I agree totally with merging @Field and @Property, the use of
@Persistent is not appropriate.

@PersistenceCapable
public class MyClass
{
    @Persistent(persistenceModifier=FieldPersistenceModifier.NONE)

This is another anomaly: FieldPersistenceModifier should become PersistenceModifier.

    String someFieldThatIsNotPersistent
}


so I tag a field that is not persistent with @Persistent ?

Doesn't bother me as much as duplicating Field/Property all over.

How about creating a new tag like @NotPersistent. To go along with @Transactional and @Persistent.

Any other idea for name? that suggests field/method/property ?

Since you agree with the direction, I'll try to plumb the depths of my vocabulary...

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!

Attachment: smime.p7s
Description: S/MIME cryptographic signature

Reply via email to