AW: AW: AW: Orchestra beginner question: conversation.flash behaves like request scope - Different solution

question: conversation.flash behaves like request scope Mario Ivankovits schrieb: Are you using persistence from within the timeChainJSF bean? If not, you can inject the bean into your controller bean and use it through your controller. This is the solution I'd prefer. Should elaborate

AW: AW: Orchestra beginner question: conversation.flash behaves like request scope

Hi Simon, thanks for your help. After I had given the conversation a name, everything worked fine. I`ve got a last question: May I specify more than one conversationName per bean? Because I`m using the same bean in different workflows. E.g: bean id=timeChainJSF

Re: AW: AW: Orchestra beginner question: conversation.flash behaves like request scope

Stephan Frai schrieb: Hi Simon, thanks for your help. After I had given the conversation a name, everything worked fine. I`ve got a last question: May I specify more than one conversationName per bean? Because I`m using the same bean in different workflows. E.g: bean id=timeChainJSF

Re: AW: AW: Orchestra beginner question: conversation.flash behaves like request scope

Hi! Or do I have to define two separate beans in Spring: bean id=timeChainJSF_1 class=com.playoli.timeperiod.jsf.TimeChainJSF bean id=timeChainJSF_2 class=com.playoli.timeperiod.jsf.TimeChainJSF You need to use the two separate bean definitions approach. That gives your EL

Re: AW: AW: Orchestra beginner question: conversation.flash behaves like request scope

Mario Ivankovits schrieb: Are you using persistence from within the timeChainJSF bean? If not, you can inject the bean into your controller bean and use it through your controller. This is the solution I'd prefer. Should elaborate a little bit more about what I meant here. If possible,