Description of problem: The s:cache enabled attribute default is false. Version-Release number of selected component (if applicable): WFK 2.1.0.CR2 jboss-seam-2.3.0.Final-redhat-1 How reproducible: Always Steps to Reproduce: 1. Deploy the blog example 2. go to http://127.0.0.1:8080/seam-blog/entry/seamtext 3. notice that no infinispan is started in the server logs Actual results: No infinispan startup messages in the server logs Expected results: infinispan should be starting when a first entry is rendered and it should be caching the blog entry Additional information: Adding an 'enabled="true"' to the entry.xhtml s:cache element <s:cache key="entry-#{blogEntry.id}" region="pageFragments" enabled="true"> seems to fix the problem, so the problem is indeed the default value of the "enabled" attribute.
Marek, is this a regression from previous version? E.g. was the cache in Seam 2.2 set to true by default?
yes, it is a regression. Basically Seam 2.2 uses Richfaces CDK 3 for generation of face-config.xml and we migrated to Richfaces CDK 4.2.3, which is a kind of PITA.
Is this something we can put into Seam 2.2 -> Seam 2.3 migration guide?
I'd prefer a release note, it doesn't make sense to turn this behavior into a feature.
Move to WFK 2.2 and release note for WFK 2.1 per 19-Nov triage call.
fixed by relying only on RF CDK annotation - https://source.jboss.org/browse/Seam/branches/enterprise/WFK-2_1/jboss-seam-ui/src/main/java/org/jboss/seam/ui/component/UICache.java?r1=15259&r2=15366
Verified on WFK 2.2.0.ER1
Doc Text updated.
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.