[jboss-cvs] JBossAS SVN: r105518 - projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US.

[jboss-cvs-commits at lists.jboss.org]

Author: misty at redhat.com
Date: 2010-06-01 19:28:48 -0400 (Tue, 01 Jun 2010)
New Revision: 105518

Modified:
   projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Cache.xml
Log:
JBPAPP-4387

Modified: projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Cache.xml
===================================================================
--- projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Cache.xml	2010-06-01 23:26:48 UTC (rev 105517)
+++ projects/docs/enterprise/EAP/trunk/5.x/Seam_Reference_Guide/en-US/Cache.xml	2010-06-01 23:28:48 UTC (rev 105518)
@@ -196,7 +196,7 @@
 			Now you can inject the cache into any Seam component:
 		</para>
 		 
-<programlisting language="Java" role="JAVA"><![CDATA[@Name("chatroomUsers") 
+<programlisting language="Java" role="JAVA">@Name("chatroomUsers") 
 @Scope(ScopeType.STATELESS) 
 
 public class ChatroomUsers { 
@@ -209,8 +209,7 @@
       cacheProvider.put("chatroom", "userList", userList); 
     } return userList; 
   } 
-}
-]]></programlisting>
+}</programlisting>
 		 <para>
 			If you want multiple cache configurations available to your application, use <filename>components.xml</filename> to configure multiple cache providers:
 		</para>
@@ -234,7 +233,7 @@
 			<literal>&lt;s:cache&gt;</literal> stores some rendered content that is rarely updated. For example, the welcome page of our blog displays recent blog entries:
 		</para>
 		 
-<programlisting role="XHTML"><![CDATA[<s:cache key="recentEntries-#{blog.id}" region="welcomePageFragments"> 
+<programlisting language="XML" role="XML"><![CDATA[<s:cache key="recentEntries-#{blog.id}" region="welcomePageFragments"> 
   <h:dataTable value="#{blog.recentEntries}" var="blogEntry"> 
     <h:column> 
       <h3>#{blogEntry.title}</h3> 
@@ -252,13 +251,12 @@
 			The <literal>&lt;s:cache&gt;</literal> cannot tell when the underlying data is updated, so you will need to manually remove the cached fragment when a change occurs:
 		</para>
 		 
-<programlisting language="Java" role="JAVA"><![CDATA[public void post() { 
+<programlisting language="Java" role="JAVA">public void post() { 
   ... 
   entityManager.persist(blogEntry); 
   cacheProvider.remove("welcomePageFragments", 
                        "recentEntries-" + blog.getId()); 
-}
-]]></programlisting>
+} </programlisting>
 		 <para>
 			If changes need not be immediately visible to the user, you can set up a short expiry period on the cache node.
 		</para>