Viktor,
i finally got someone on the hibernate IRC channel to take a look at the
problem. He claims that if he removes the final declarator from a field for
which i have only a getter and then adds a setter hibernate works as
advertised. i will test this out. If no joy i might take you up on your
All,
Can anyone recommend an alternative to hibernate for a JPA implementation?
i've been stuck on this bug for several days, now; i need to move on.
Best wishes,
--greg
On Thu, Jun 18, 2009 at 2:09 PM, Meredith Gregory
lgreg.mered...@gmail.comwrote:
Viktor,
i finally got someone on the
Ah, this makes sense to me. Final fields in Hibernate-manage objects
will almost certainly cause problems in my experience (at least using
field-based access; I've no experience with property-based mappings.)
Kris.
On Thu, Jun 18, 2009 at 3:09 PM, Meredith
Gregorylgreg.mered...@gmail.com wrote:
Is this final field something that is intended to be retrieved from the DB?
As far as I know, JPA doesn't support final fields, period. If this getter
is really just wrapping something else, it should be marked as @Transient.
Derek
On Thu, Jun 18, 2009 at 4:09 PM, Meredith Gregory
Derek, Kris,
Thanks. The problem is more subtle. i have modified my code emitter to not
mark the field as final and to add the setter. i still get the same problem.
However, i've got sample code derived from the emitted code that generates
the correct schema. That is the key is used, not a
