This content has been marked as final.
Show 7 replies
-
1. Re: Bug with EVENT scope
pmuir Sep 3, 2007 5:08 PM (in response to andreigh.ts)This is due to differences between EVENT scoped POJOs and Stateless EJB3s. SLSBs are drawn from a pool for each method invocation, and no guarantee is made about whether this bean has been used before. Whilst an EVENT scoped POJO is created for each request. No bug.
-
2. Re: Bug with EVENT scope
andreigh.ts Sep 4, 2007 4:14 AM (in response to andreigh.ts)So if I understand correctly, when using SLSB, it is possible that the container serves the same object, because of caching.
-
3. Re: Bug with EVENT scope
pmuir Sep 4, 2007 4:32 AM (in response to andreigh.ts)Yes, this is how EJB3 works.
-
4. Re: Bug with EVENT scope
andreigh.ts Sep 4, 2007 5:51 AM (in response to andreigh.ts)Thanks.
Please note the following bug in the seam 2 documentation: in chapter 3.1.4(Conversation context), it says that:
Some conversations last for just a single request. Conversations that span multiple requests must be demarcated using annotations provided by Seam.
When using redirect for displaying the view, the conversation context spans multiple requests, even if no special annotations are used (and the conversation is not long running). -
5. Re: Bug with EVENT scope
pmuir Sep 4, 2007 6:11 AM (in response to andreigh.ts)How do you mean "redirect" - the redirect element in pages.xml?
-
6. Re: Bug with EVENT scope
andreigh.ts Sep 4, 2007 7:08 AM (in response to andreigh.ts)Yes, redirect in pages.xml. I suppose it does a browser redirect that generates a new http request.
-
7. Re: Bug with EVENT scope
pmuir Sep 13, 2007 5:34 AM (in response to andreigh.ts)This is correct, and explained in the docs.