Hi Marina,
On Tue, Nov 21, 2006 at 12:32:32AM -0800, Marina Vatkina wrote:
> Explicit or implicit type of LAZY causes the problem as it results in class
> modifications by TopLink Essentials to support the lazy load (the runtime
> needs to be notified that it's time to load the field as it's been
> accessed).
>
> If fetch type EAGER solves your problem, you don't need to worry about
> anything
> else. Otherwise you might need to do static weaving of your client side
> entity
> classes before packaging.
Thanks again. I assumed that only having an implicit fetchtype would make
Toplink modify the classes.
Thanks, Wouter
--
People: "If she weighs the same as a Duck, she's made of wood!"
Sir Bedevere: "And therefore...?"