Based on the outcome of this discussion, I will add a few issues to our issue tracker which amount to these proposals.
Matthias, did you already sign up to be a mentor? Did anyone else do so already? Who wants to mentor? best regards, Martin On 3/11/10, Martin Marinschek <mmarinsc...@apache.org> wrote: >> - 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. > > ok, sure - this could be part of the project. > >> But what does this have to do with trinidad's pageFlowScope? > > If there is common utiltiy methods we can re-use (for example for > file-->new window detection in IE with JavaScript the generation of > this JavaScript), we can and should certainly reuse it. > >> 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. > > perfect - let's do a proposal for this. > > best regards, > > Martin > -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces
