-
1. Re: javassist.JavassistLazyInitializer exception when Querying
adamw Mar 4, 2010 8:43 AM (in response to getboa)Is the Hibernate Session closed after doing the query, and before displaying the web page?
Adam
-
2. Re: javassist.JavassistLazyInitializer exception when Querying
getboa Mar 4, 2010 11:19 AM (in response to adamw)Hi Adam...
Well as i'm working with Seam, the problem might be there, the hibernate session's been closed after querying, if i set the scope to Session, it works fine... i'll dig into more to figure out.
-
3. Re: javassist.JavassistLazyInitializer exception when Querying
adamw Mar 7, 2010 9:41 AM (in response to getboa)Hmm... the session should be opened on request start and finished on request end. You are saying you changed a scope of a bean to session and it started working? What was the scope before?
Adam
-
4. Re: javassist.JavassistLazyInitializer exception when Querying
getboa Mar 8, 2010 7:25 AM (in response to adamw)Yes Adam, when i changed to Session, it worked fine, even pagination with rich:dataScroller...The scope before was Page, didn't work and throws this JavassistLazyInitializer exception when trying to show the results on page.... tried with scope Conversation, it shows the result in my dataTable, but pagination does not work... Weird isn't it? -
5. Re: javassist.JavassistLazyInitializer exception when Querying
adamw Mar 9, 2010 2:56 AM (in response to getboa)That's very weird . Only thing that comes to my mind is that the error occured in the view reconstruction phase, that is, in one request you create a component, read the values, render it, then the request comes back and the view is re-constructed, and tries to access old values. However still, this shouldn't happen as the values were read before. But maybe you could verify if this was this scenario?
Adam
-
6. Re: javassist.JavassistLazyInitializer exception when Querying
getboa Mar 10, 2010 3:51 PM (in response to adamw)I decided to change the way that these records are going to be shown; as this query will bring a lot of records(i didn't know about it before) i did choose to show'em as a report.
By the way... thank Adam and if someone else pass through this in the future, post back how you fixed that's a curious issue