Hi Marina,
On Mon, Nov 20, 2006 at 11:56:57PM -0800, Marina Vatkina wrote:
> This seems like the problem discussed on the users_at_glassfish thread to
> which I replied today:
> https://glassfish.dev.java.net/servlets/ReadMsg?list=users&msgNo=1452
>
> Does it make sense? OneToMany side of the relationship defaults to
> the fetch type LAZY.
Thanks for your reply. I saw your reply on the users_at_glassfish list, but I
didn't connect it to my problem.
I think your explanation does make sense. Would this mean that making the fetch
type (be it eager or lazy) explicit, the ClassCastException shouldn't happen? I
figure that in that case Toplink won't have to modify the class.
When I set it explicitly to eager I don't get any errors but I figured that was
because all rows were fetched and transfered to my client. The client, by the
way, is NOT a Java EE Client so that may explain me getting the error.
I will explicitly set the fetch type to lazy and see if I still don't get any
errors.
Thanks! Wouter
--
People: "If she weighs the same as a Duck, she's made of wood!"
Sir Bedevere: "And therefore...?"