[EMAIL PROTECTED] schrieb:
Simon, thank for the response.
I tried to read the documentation but I don't really anderstand what
Orchestra do. I understood that Orchestra give the possibility to define
a Managed Bean with a scope "Conversation". But how can start a
conversation?
A conversation is started at the time the bean is accessed, this was a
design decision realtively early on in the development of Orchestra.
The point simply is that in most if not all cases manual conversation
triggering is not needed because as soon as you need a bean which is
declared as conversational you expect it to be under conversation anyway.
It also makes more sense in the way spring handles its scopes which
follow a similar route of declaring a bean scope in spring and then
expecting the bean to be under that scope.
If you need to bind beans which have lifetimes than your conversational
bean you always can use aop:scope proxy to weave a proxy around those beans.
This way you can bind a conversational bean to an application or
sesssion scoped bean without making a mem leak.
