[
https://issues.apache.org/jira/browse/ORCHESTRA-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Clemente Biondo updated ORCHESTRA-54:
-------------------------------------
Status: Patch Available (was: Open)
> Support for wildcard globbing in property ignoreViewIds of
> AccessScopeManagerConfiguration bean.
> -------------------------------------------------------------------------------------------------
>
> Key: ORCHESTRA-54
> URL: https://issues.apache.org/jira/browse/ORCHESTRA-54
> Project: MyFaces Orchestra
> Issue Type: Improvement
> Components: Conversation
> Affects Versions: 1.4
> Reporter: Clemente Biondo
> Priority: Minor
>
> Support for wildcard globbing in property ignoreViewIds of
> AccessScopeManagerConfiguration bean.
> Recently i've faced the same problem discussed in this thread:
> http://www.mail-archive.com/[email protected]/msg47621.html
> When a Richfaces custom resource (like for example a xcss style sheet)
> is rendered it runs a complete JSF lifecycle, including all
> the post-render phase listeners.
> This invalidates all the "access" scope conversations in the current
> conversation context.
> AccessScopeManagerConfiguration provides a property named ignoreViewIds
> that allows to ignore specific view names. However this property supports
> only fixed view names.
> I've provided a patch to add support for wildcard globbing, so Orchestra's
> AccessScopeManagerConfiguration class can
> be configured in spring to ignore richfaces custom resources with the
> following code:
> <bean
>
> name="org.apache.myfaces.orchestra.conversation.AccessScopeManagerConfiguration"
>
> class="org.apache.myfaces.orchestra.conversation.AccessScopeManagerConfiguration"
> scope="singleton">
> <property name="ignoreViewIds">
> <set>
> <value>*.xcss*</value>
> </set>
> </property>
> </bean>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
