Hi guys,
I need your opinion regarding this "issue" :
The persistence classes get more complex as the application grows and
gets more complex. For my question, consider the following example:
Animal {
long id,
float weight,
float speed
}
JungleAnimal extends Animal {
List<Animal> breakfast;
}
Lion extends JungleAnimal {
boolean isMale
}
So we have a simple class hierarchy, everything works with GAE (I have
simplified code above and it turned out to not be Java anymore) -
Animal implements Serializable, it is annotated with
@PersistenceCapable, all fields have @Persistent, etc.
So, now that I have this basic framework, I write an insert method for
Lion and this method will write all the fields inherited from
hierarchy.
The question is, did anybody think about having some DAOs for each
class, and each of them being concerned with the fields from that
class alone (and calling additional DAOs as the fields need to be
persisted up in the hierarchy)? Is that even possible?
Thanks, I hope everything is clear. I would really appreciate your
opinion on this matter,
Alex
--
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 [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
