[
https://issues.apache.org/jira/browse/ORCHESTRA-65?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13972974#comment-13972974
]
Leonardo Uribe commented on ORCHESTRA-65:
-----------------------------------------
I have already committed a prototype of the option 3 into MyFaces Orchestra.
Now the next step is create a new module called core22-extra-mfcore that
contains an implementation of the view scope and flow scope for MyFaces Core
2.2.x. We cannot do this part compatible with Mojarra, because there are some
implementation details that we cannot bypass like for example hook the view /
flow scope map or catch when the session is destroyed or the view scope map, so
that's why we are going to put this in a independent module.
> Create artifacts compatible with JSF 2.2
> ----------------------------------------
>
> Key: ORCHESTRA-65
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-65
> Project: MyFaces Orchestra
> Issue Type: Task
> Reporter: Leonardo Uribe
> Assignee: Leonardo Uribe
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
