Hi Gordon,
Thanks for the reply. I will post it to the forum and ask them to try
more recent Glassfish builds.
They are using SJSAS 9.0 PE FCS.
Cheng
Gordon Yorke wrote:
> This is most likely a manifestation of glassfish issue 850 which was fixed late July. What version of TopLink Essentials are they using?
> --Gordon
>
> -----Original Message-----
> From: Cheng.Fang_at_Sun.COM [mailto:Cheng.Fang_at_Sun.COM]On Behalf Of Cheng
> Fang
> Sent: Wednesday, October 18, 2006 8:47 AM
> To: persistence_at_glassfish.dev.java.net
> Subject: [forum question] Query sent to unactivated unitofwork
>
>
> Hi,
>
> Could someone look into this problem?
>
> http://gceclub.sun.com.cn/NASApp/sme/jive/thread.jsp?forum=22&thread=40971
>
>
> I've asked the user to post source code and descriptors. The original
> posts are in Chinese. I've translated the relevant part in English below:
>
> He's using NetBeans 5.5 beta, SJSAS PE 9.0. Have a stateful session
> bean invoking entities. The data has been saved to database, but the
> stateful bean couldn't view the data thru entity operation. After
> restarting the server, the stateful bean was able to view the data.
>
> OneToMany(mappedBy = "gsid",cascade=CascadeType.ALL,fetch=FetchType.EAGER)
>
> Is it related to fetch=FetchType.EAGER?
>
> When he set fatch-type to LAZY, he saw this error: Query sent to
> unactivated unitofwork. Once he changed it to EAGER, the stateful bean
> can't view the data.
>
> ----------------
>
> Thanks,
>
> Cheng
>