"CptnKirk" wrote : @Out's scope defaults to the scope of the enclosing controller, in this case the SLSB. SLSB have a stateless scope. I think that Seam may actually promote the outjection of context variables of stateless components to event scope for you (but I'm not positive). | | Event scope is like JSP request scope and page scope is like JSP page scope. My guess is this example didn't work for you because you used navigation in your JSF action. If so, your view came in two requests. The first outjected the Bean, then left scope. Then you made the next request to view the page and saw everthing with their original values. | | I hope this clears up the scoping question.
I'm experiencing this very problem(although, I'm using SFSB). The only way I can get my application to work with outjection is to set everything to SESSION scope. I do use page navigation and as soon as I change scope to anythign less than SESSION, nothing gets outjected. In another post Gavin says SESSION scope is bad and it is a memory leak. Now I'm really worried. How do you solve this problem? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3999581#3999581 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3999581 _______________________________________________ jboss-user mailing list jboss-user@lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-user
