2010/3/9 Mario Ivankovits <ma...@ops.co.at> > Hi! > > > > *From:* Leonardo Uribe [mailto:lu4...@gmail.com] > *Sent:* Tuesday, March 09, 2010 7:54 PM > *To:* MyFaces Development > *Subject:* Re: Google SoC > > > > > > > > - Extend Orchestra use Conversations based on the JSF 2.0 custom scope > API, Extend Orchestra to work with Spring Conversations, to do > File->New Window Handling > > > I was thinking based on a suggestion done on JSFDays to take advantage on > trinidad pageFlowScope code (like we did with flash scope on myfaces 2.0), > and refactor that code to allow orchestra conversation scope work without > spring (using the new JSF 2.0 custom scope). > > * * > > * [Mario Ivankovits] Orchestra without Spring, that surely would be great. > One thing to keep in mind is that we need AOP or at least proxying to inject > the current conversation into the bean. Not too complicated, though.* > > *But what does this have to do with trinidad's pageFlowScope?* > The code behind pageFlowScope could be used to create a conversational scope. It is just that code has some utility stuff that could be used.
> *If we leave the EntityManager thing out of line, we just need a JSF 2.0 > scope impl and the proxying/interception stuff which is handled by Spring > currently.* > > > > *Ciao,* > > *Mario* >
