[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1891) Decouple page fragment caching from JBoss Cache

[Pete Muir (JIRA)]

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

Pete Muir commented on JBSEAM-1891:
-----------------------------------

based on Sebastians patch I implemented everything I wrote above, and also used abstract superclasses for common functionality, used the cacheProvider name throughout (w/ the classname in components.xml being used to select the correct provider), added an XSD, added a JBoss POJOCache provider for 1, simplified the cache region stuff to just have a single default region which is configurable from components.xml.

I fiddled the build script to compile the JBoss Cache 1 stuff against JBoss Cache 1 and the JBoss Cache 2 stuff against JBoss Cache 2

Still need to update the docs and the example to show the new configuration.

> Decouple page fragment caching from JBoss Cache
> -----------------------------------------------
>
>                 Key: JBSEAM-1891
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-1891
>             Project: Seam
>          Issue Type: Task
>          Components: Core, JSF Controls
>            Reporter: Christian Bauer
>            Assignee: Pete Muir
>            Priority: Critical
>             Fix For: 2.1.0.BETA1
>
>         Attachments: alternative_cache_provider_for_the_page_fragment_cache.patch
>
>
> The code in UICache and PojoCache only works with this component:
>       return (org.jboss.cache.aop.PojoCache) Component.getInstance(PojoCache.class, ScopeType.APPLICATION);
> Make this generic so that other cache providers can be used.

-- 
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