[jbosscache-commits] JBoss Cache SVN: r8332 - in enterprise-docs/tags/JBoss_EWP_5_0_0: Cache_User_Guide/en-US and 1 other directory.

[jbosscache-commits at lists.jboss.org]

Author: laubai
Date: 2010-02-01 20:20:52 -0500 (Mon, 01 Feb 2010)
New Revision: 8332

Modified:
   enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/General_FAQ.xml
   enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/TreeCache_FAQ.xml
   enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml
Log:
Added changes for EWP5; JBPAPP-3498.

Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/General_FAQ.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/General_FAQ.xml	2010-01-21 05:44:24 UTC (rev 8331)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/General_FAQ.xml	2010-02-02 01:20:52 UTC (rev 8332)
@@ -123,7 +123,7 @@
                 </answer>
             </qandaentry>
 
-            <qandaentry>
+            <!--<qandaentry>
                 <question>
                     <para>Can I run JBoss Cache outside of the JBoss Enterprise Web Platform?
                     </para>
@@ -139,7 +139,7 @@
                         details.
                     </para>
                 </answer>
-            </qandaentry>
+            </qandaentry>-->
 
             <qandaentry>
                 <question>
@@ -194,4 +194,4 @@
                 </answer>
             </qandaentry> -->
         </qandaset>
-    </chapter>
\ No newline at end of file
+    </chapter>

Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/TreeCache_FAQ.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/TreeCache_FAQ.xml	2010-01-21 05:44:24 UTC (rev 8331)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_FAQ/en-US/TreeCache_FAQ.xml	2010-02-02 01:20:52 UTC (rev 8332)
@@ -284,11 +284,15 @@
 
                 <answer>
                     <para>
-                        JBoss Cache supports any TransactionManager that is <ulink url="http://java.sun.com/products/jta/">JTA</ulink> compliant such as <ulink url="http://www.jboss.org/jbosstm/">JBoss Transactions</ulink>.
+                        JBoss Cache supports any TransactionManager that is <ulink url="http://java.sun.com/products/jta/">JTA</ulink> compliant, such as <ulink url="http://www.jboss.org/jbosstm/">JBoss Transactions</ulink>.
                     </para>
                     <para>
                         While JBoss Cache does ships with a dummy transaction manager (<literal>org.jboss.cache.transaction.DummyTransactionManager</literal>), we do <emphasis>not</emphasis> recommend using this for production. It is not thread safe, and is intended for internal testing only.
                     </para>
+                    <important>
+                      <title>JTS is not supported</title>
+                      <para>Java Transaction API (JTA) is supported for use with Enterprise Web Platform. However, Java Transaction Service (JTS) is not supported. Keep this in mind when selecting a transaction manager.</para>
+                    </important>
                 </answer>
             </qandaentry>
 
@@ -563,4 +567,4 @@
             </qandaentry>
 
         </qandaset>
-    </chapter>
\ No newline at end of file
+    </chapter>

Modified: enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml
===================================================================
--- enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml	2010-01-21 05:44:24 UTC (rev 8331)
+++ enterprise-docs/tags/JBoss_EWP_5_0_0/Cache_User_Guide/en-US/deployment.xml	2010-02-02 01:20:52 UTC (rev 8332)
@@ -34,8 +34,7 @@
       
       <para>
          If, after deploying your cache you wish to expose a management interface
-         to it in JMX, see the
-         <xref linkend="jmx.registration.programatic" />.
+         to it in JMX, see <xref linkend="jmx.registration" />.
       </para>
    </section>
    <section id="deployment.microcontainer">
@@ -337,8 +336,7 @@
 ]]></programlisting>
 
             <para>
-               As discussed in the <xref linkend="jmx.registration.programatic" />
-               section, <literal>CacheJmxWrapper</literal> can do the work of building, creating and starting the
+               <literal>CacheJmxWrapper</literal> can do the work of building, creating and starting the
                <literal>Cache</literal> if it is provided with a <literal>Configuration</literal>. With the
                microcontainer, this is the preferred approach, as it saves the boilerplate XML
                needed to create the <literal>CacheFactory</literal>.