Details
-
Task
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
In JSF 2.2 it was included a solution for manage client windows logic and state. It was inspired in MyFaces Orchestra, but as a side effect now the artifacts for JSF 2.0 are no longer compatible with 2.2, because they overlap the same logic. MyFaces Orchestra used a request parameter called "conversationId" but now jsf defined a new param for that.
Additionally, MyFaces Orchestra can be a good place to provide custom implementations for some features that depends on MyFaces Core SPI interface like:
- Spring variant of ViewScope
- Spring variant of FlowScope
Since there are some important changes, the idea is do not follow the strategy used in jsf 2.0 (use myfaces builder plugin unpack goal) and copy the files in a new module.
Attachments
Issue Links
- relates to
-
ORCHESTRA-63 JSF 2.2.5 - Compatibility for Orchestra
- Open