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

Przemyslaw Jaskierski (JIRA) jira-events at lists.jboss.org
Wed Jul 30 09:48:25 EDT 2008


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

Przemyslaw Jaskierski commented on JBSEAM-1891:
-----------------------------------------------

Please remove these comment-outputting lines

 writer.write("<!-- cached content for: ");
 writer.write(key);
 writer.write(" -->");
 ...
 writer.write("<!-- end of cached content -->");

These were removed from the original implementation in the 2.1 branch because of an another request AFAIR (?).
BTW exposing internal information is almost never a good idea.

Thanks for this patch!


> 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
>             Fix For: 2.1.0.BETA2
>
>         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

        



More information about the seam-issues mailing list