More Hibernate than Seam question

[drapierwim]

Maybe somebody could help me out with some lazy loading stuff.

I understand that hibernate uses by default lazy loading for collections
now I have an Object 'a' with child objects like 'a1' and so on... that has also childeren 'a11' ... and so on... util my deepest object represents an object with six digits like 'a115400' for example.

Now the problem is when I get to a dept of 3 digits and trying to get his childeren I get an exception.

I also like to mention that this was worked fine when my SFSB lived in the ConversationContext now it's in the SessionContext or is this irrelavant

javax.faces.FacesException: Error calling action method of component with id _id0_1:_id2
 at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:74)
 at javax.faces.component.UICommand.broadcast(UICommand.java:106)
 at javax.faces.component.UIData.broadcast(UIData.java:338)
 at javax.faces.component.UIViewRoot._broadcastForPhase(UIViewRoot.java:90)
 at javax.faces.component.UIViewRoot.processApplication(UIViewRoot.java:164)
 at org.apache.myfaces.lifecycle.LifecycleImpl.invokeApplication(LifecycleImpl.java:271)
 at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:86)
 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:94)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.myfaces.component.html.util.ExtensionsFilter.doFilter(ExtensionsFilter.java:122)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
 at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
 at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
 at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
 at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
 at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)
 at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
 at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
 at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
 at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
 at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
 at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
 at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
 at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
 at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
 at java.lang.Thread.run(Thread.java:595)
Caused by: javax.faces.el.EvaluationException: /accounts.xhtml @26,33 action="#{accountsManager.getChilderen}": javax.ejb.EJBException: null; CausedByException is:
 ivvo.drapier.model.DetailAccount
 at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:73)
 at org.apache.myfaces.application.ActionListenerImpl.processAction(ActionListenerImpl.java:63)
 ... 29 more
Caused by: javax.ejb.EJBException: null; CausedByException is:
 ivvo.drapier.model.DetailAccount
 at org.jboss.ejb3.tx.Ejb3TxPolicy.handleExceptionInOurTx(Ejb3TxPolicy.java:46)
 at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:70)
 at org.jboss.aspects.tx.TxInterceptor$Required.invoke(TxInterceptor.java:134)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
 at org.jboss.aspects.tx.TxPropagationInterceptor.invoke(TxPropagationInterceptor.java:61)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
 at org.jboss.aspects.security.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:63)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
 at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:32)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
 at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousInterceptor.java:91)
 at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:98)
 at org.jboss.ejb3.stateful.StatefulContainer.localInvoke(StatefulContainer.java:136)
 at org.jboss.ejb3.stateful.StatefulLocalProxy.invoke(StatefulLocalProxy.java:83)
 at $Proxy105.getChilderen(Unknown Source)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.sun.el.parser.AstValue.invoke(AstValue.java:130)
 at com.sun.el.MethodExpressionImpl.invoke(MethodExpressionImpl.java:274)
 at com.sun.facelets.el.TagMethodExpression.invoke(TagMethodExpression.java:68)
 at com.sun.facelets.el.LegacyMethodBinding.invoke(LegacyMethodBinding.java:69)
 ... 30 more

[drapierwim]

Just as I suspected lazy collection loading works with a SFSB in a ConversationContext if the SFSB is placed in the SessionContext it fails after the third fetching!!!

Did I found my first bug?

[gavin.king]

Lazy loading works inside a persistence context.

So it depends what is the scope of your persistence context. If you are using:

@PersistenceContext
EntityManager em;

Then you have a container-managed PC that is open only for the scope of the transaction.

@PersistenceContext(type=EXTENDED)
EntityManager em;

Then you have a container-managed PC that is open whenever a transaction is running, for the lifetime of the SFSB. If you are using:

@In(create=true)
EntityManager em;

then what you have is a (Seam-managed) conversation-scoped PC and it will be open only for the scope of the conversation.

You can only lazy-fetch within the scope of a PC (for all kinds of excellent reasons).

It would not usually make sense to have a conversation-scoped PC on a session-scoped SFSB.