I mistakenly annotated one of my Seam classes as Stateless and then applied it
to the EVENT Seam scope. Clearly this is not correct and I've since fixed it
such that the component is now stateful. Here is my original code.
| @Stateless // <-- This should have been @Stateful
| @Scope(ScopeType.EVENT)
| @Name("browseAccountBean")
| @Interceptors(SeamInterceptor.class)
| public class BrowseAccountBean implements Serializable, BrowseAccount {
| ...
| }
|
The bean was remembering state over multiple requests which is not surprising
in hindsight and was confusing until I spotted the bug.
Perhaps Seam should have picked up on my bad annotations and thrown an
exception? (not that Seam is to blame)
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3934402#3934402
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3934402
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
