Rick Curtis wrote: > >> At first someone knows a solution for that problem (workaround)? > > Does this comment from the JIRA apply to your situation? : Forgot to > mention > that one work around we found for this problem is that if both Lower > entities use LAZY fetches in stead of EAGER fetches, then the exception > won't be thrown. > > hth, > Rick > I tried this workaround but it doesnt work - If I save the n:m dependency all doing wright. If I load the object (LAZY) all doing wright, but if I wanna load the object with are not loaded (calling getXxx) I getting the exception. Or does the comment talking about some different solution as: @ManyToMany(cascade = CascadeType.REFRESH, fetch = FetchType.LAZY)
Kevin Sutter wrote: > > Since you are a WebSphere user, have you opened a PMR for this problem? > If > you open a PMR, that will definitely raise the priority of getting this > issue resolved and get a fix delivered in an iFix or fixpack. Literally, > anybody can open a JIRA Issue against OpenJPA. The community only has so > many cycles in a day, so we need some assistance with prioritizing the > work. PMRs help the IBM-related developers properly prioritize... :-) > Where can I open a "PMR"? I just posted the hibernate "problem" https://www.ibm.com/developerworks/forums/thread.jspa?threadID=235106&tstart=0 Furthermore I need a solution within the next few days :( Kevin Sutter wrote: > > Related to getting Hibernate to work properly in WebSphere. It's > definitely > doable [1], but I would ask why you want to use yet another piece of > software in your stack? I've been asked this question so many times that > I > recently wrote a Comment Lines to document my response [2]. > > Hope this information helps. > > Thanks! > Kevin > I wanna use another persistence provider because I need a solution for the bug. -- View this message in context: http://openjpa.208410.n2.nabble.com/WAS7-persistence-provider-problems-openJPA-Hibernate-tp5514291p5514556.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
