This content has been marked as final.
Show 5 replies
-
1. Re: Conversation Beans and Session scoped beans resulting in
mars1412 Jan 23, 2008 6:19 AM (in response to limousyf)just some thoughts:
- are you sure, the GestionAffichage bean has already been created and exists in the session scope?
- maybe the GestionAffichage cannot be created (for any reason) and thus the activitesByCollaborateurCrossData cannot be created.
- it's also strange, that the activitesByCollaborateurCrossData interface starts with lowercase (and also the bean class) and is the same as the Seam component name
note: I am a newbie myself and I haven't seen the errormessage "Could not find stateful Bean" yet
- are you sure, the GestionAffichage bean has already been created and exists in the session scope?
-
2. Re: Conversation Beans and Session scoped beans resulting in
limousyf Jan 23, 2008 6:39 AM (in response to limousyf)Well I guess the gestionAffichageBean is created; I think I could add the "create=true".
But, as I deference the beangestionaffichage.afficherMenuActiviteParCollaborateur()
I would have a NPE if it wasn't created.
The names are clearly incorrect (intern work :) ) but I don't think that it's a problem here. -
3. Re: Conversation Beans and Session scoped beans resulting in
limousyf Jan 24, 2008 4:20 AM (in response to limousyf)Just a question.
The session-scoped bean was stateful at the beginning, which was clearly a mistake (man, I love interns !).
Is it possible that the stateful session-scoped bean is destroyed at conversation timeout ?
Or when another conversation using this bean stops ? (maybe it's moved from session scope to conversation scope, then destroyed at conversation ending).
I thought that because I saw10:06:26,171 INFO [STDOUT] Mort du Bean GestionConfigurationBean Scope = Application
in my log, which is the message lauched when a bean is destroyed.
In this case, it's a stateful application-scoped bean (please god save me from internicide).
It's clearly another mistake here, but the fact is that my application-scoped bean is destroyed !
I don't know if it's a bug or a feature ...
Regards -
4. Re: Conversation Beans and Session scoped beans resulting in
pmuir Jan 24, 2008 8:17 AM (in response to limousyf)Post the exception and stack trace.
The session-scoped bean was stateful at the beginning, which was clearly a mistake (man, I love interns !).
Why is making a session scoped bean @Stateful a mistake?Is it possible that the stateful session-scoped bean is destroyed at conversation timeout ?
No -
5. Re: Conversation Beans and Session scoped beans resulting in
limousyf Jan 24, 2008 8:39 AM (in response to limousyf)Well it was a clear mistake in that case: the conversation was opened at the bean creation and never closed.
Well, I'll try to reproduce the bug and post the stacktrace