Hi I have been working for some time in this issue:
https://issues.apache.org/jira/browse/ORCHESTRA-65 The idea is create artifacts compatible with JSF 2.2. Since MyFaces Orchestra replicated the window id stuff that was properly standarized in 2.2, it is necessary to do some changes over how it works. The old trick still works using orchestra 2.0 + jsf 2.2 or orchestra 2.2 + jsf 2.2 without client window enabled. The proposed solution was already commited. The thing is JSF 2.2 does not provide a way to use the new flow scope without CDI. The flow scope map works, but the scope does not. The same applies for the view scope. In MyFaces 2.2 we added some interfaces: org.apache.myfaces.spi.ViewScopeProvider org.apache.myfaces.spi.FacesFlowProvider To deal with the necessary logic. It is known that Spring does not manage bean serialization problem, and in that sense CDI is better, but there are still users who use the combination between JSF / Spring and since Orchestra is the library that helps to fill the gap, I would like to propose the creation of a new extra module to hold the implementation for these two scopes there. This module will be compatible only with MyFaces Core, because we cannot fill the gaps properly using standard JSF 2.2 stuff. For example, how to provide the annotated flows in the configuration step, or how to detect when enter in a flow or exit from a flow, or how to destroy the view scope beans when the page is no longer used. What do you think about this? do you believe it is a good or a bad idea? will the module be useful or not? or we should forget about, provide in Orchestra maintenance releases only and suggests users to move to CDI instead, which is a lot better and has received most of our attention the last years. regards, Leonardo Uribe
