[seam-issues] [JBoss JIRA] Commented: (JBSEAM-4525) Allow FacesMessages component to be Scope other than CONVERSATION

[Pete Muir (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBSEAM-4525?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12507245#action_12507245 ] 

Pete Muir commented on JBSEAM-4525:
-----------------------------------

Mike, are you still able to work on this, deadline for CR1 is end of January.

> Allow FacesMessages component to be Scope other than CONVERSATION
> -----------------------------------------------------------------
>
>                 Key: JBSEAM-4525
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4525
>             Project: Seam
>          Issue Type: Feature Request
>          Components: JSF Integration
>    Affects Versions: 2.2.0.GA
>            Reporter: Michael Youngstrom
>            Assignee: Michael Youngstrom
>             Fix For: 2.2.1.CR1
>
>
> The conversation scope can be a problematic scope for FacesMessages.  Often the developer may wish to end a conversation "before-redirect" and communitcate a message to the next page.  However, this doesn't work since by default FacesMessages is a conversation scoped component.
> If FacesMessages were allowed to be a Session scoped component project wouldn't have this issue at the expense of a less correct concurrency situation (multiple pages rendered at the same time from the same session may mix up messages).
> That said it would be nice to give the project a choice.  The scope for FacesMessages can be overridden to be Session scoped, however, the static :"instance()" method currently only looks in the conversation scope so the scope essentially cannot be overridden.
> This feature request is to change FacesMessages.instance() to not force lookup in the conversation scope allowing projects if they wish to override FacesMessages' scope if they wish.
> I will plan on committing the change myself for 2.2.1 unless someone objects.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira