Just a couple of questions about design decisions, if I may.
The first is about needing a *public* default constructor. In other
places hibernate will access non-public methods (e.g. property get/set
methods), so I was wondering if it was a concious decision NOT to do the
same for the default constructor of a presistent capable class.
The other is the "marker" interface Persistent. I'm aware of reasons why
you would / wouldn't want it, but wanted to hear from the team why it
was chosen to go this way with Hibernate.
Regards, PaulS :)
|