Bug 877374 - Seam2.3 s:cache enabled attribute is false by default
Summary: Seam2.3 s:cache enabled attribute is false by default
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise WFK Platform 2
Classification: Retired
Component: Seam
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER1
: 2.2.0
Assignee: Marek Novotny
QA Contact: Marek Schmidt
URL:
Whiteboard: Seam2.3
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-16 11:30 UTC by Marek Schmidt
Modified: 2013-05-14 14:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The s:cache element 'enabled' had an incorrect default value of 'false'. As a consequence, caching did not work by default. This has been fixed and the s:cache element has caching enabled by default.
Clone Of:
Environment:
Last Closed: 2013-05-14 14:50:37 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker JBSEAM-5057 0 None None None Never

Description Marek Schmidt 2012-11-16 11:30:51 UTC
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.

Comment 1 Karel Piwko 2012-11-16 12:40:54 UTC
Marek, is this a regression from previous version? E.g. was the cache in Seam 2.2 set to true by default?

Comment 2 Marek Novotny 2012-11-16 12:45:20 UTC
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.

Comment 3 Karel Piwko 2012-11-19 09:59:52 UTC
Is this something we can put into Seam 2.2 -> Seam 2.3 migration guide?

Comment 4 Marek Schmidt 2012-11-19 10:27:23 UTC
I'd prefer a release note, it doesn't make sense to turn this behavior into a feature.

Comment 6 mark yarborough 2012-11-19 14:47:14 UTC
Move to WFK 2.2 and release note for WFK 2.1 per 19-Nov triage call.

Comment 8 Marek Schmidt 2013-03-01 15:29:09 UTC
Verified on WFK 2.2.0.ER1

Comment 9 Sneha 2013-03-21 09:53:09 UTC
Doc Text updated.

Comment 10 Karel Piwko 2013-05-14 14:50:37 UTC
Closed as CURRENTRELEASE, part of WFK 2.2.0 distributables.


Note You need to log in before you can comment on or make changes to this bug.