We are advised to have our persistent fields accessible only thro
setter/getter and not to allow public access, less the JDO mechanism
is bypassed.

We are also advised to implement persistenceCapable interface.

However, in gae java, we don't seem to require to implement
persistenceCapable interface, but merely place @PersistenceCapable
annotation appropriately.

A setter/getter is merely

setHello(hello){this.hello = hello;}
getHello{return this.hello;}

There is nothing else in between those lines that could be bypassed.

That set me thinking ...

Does @PersistenceCapable and all the other gae @ annotations modify/
enhance my java code and insert extra stuffs into my setters/getters
during compilation which would be bypassed if those fields were
accessed directly by non-persistence aware classes?

--

You received this message because you are subscribed to the Google Groups 
"Google App Engine for Java" group.
To post to this group, send email to google-appengine-j...@googlegroups.com.
To unsubscribe from this group, send email to 
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.


Reply via email to