[appengine-java] Re: why setter getter advised when using datanucleus ?

2009-12-10 Thread datanucleus
You annotate a class with @PersistenceCapable, and then you use the
enhancer. Magic happens there and it implements the interface for
you ... you're so lucky. Why not use a Java decompiler and
decompile an enhanced class and see what you find ? that would settle
your doubts ... or just go to the Apache JDO website and there's an
example of what the enhancer does on there.

PS. If you wanted to update (persistent) fields directly (from a non-
persistent class) you could just annotate that class with
@PersistenceAware

--

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.




[appengine-java] Re: why setter getter advised when using datanucleus ?

2009-12-10 Thread Blessed Geek
Also, does @PersistenceCapable cause gae sdk to insert "implements
PersistenceCapable" for us or is it the case that gae simply/
inconsistently do not require us to implement PersistenceCapable?

--

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.