Index: lams_contentrepository/src/java/treecache.xml
===================================================================
diff -u -rd69fd0c0b6e3af330bb1ddbf3099022feca3f092 -r8774613cfd0a6e8ddbab1c14aa88f160279e1090
--- lams_contentrepository/src/java/treecache.xml	(.../treecache.xml)	(revision d69fd0c0b6e3af330bb1ddbf3099022feca3f092)
+++ lams_contentrepository/src/java/treecache.xml	(.../treecache.xml)	(revision 8774613cfd0a6e8ddbab1c14aa88f160279e1090)
@@ -44,12 +44,13 @@
 
 
 	<!-- Use DefaultCache to bind the cache into JNDI. The proxy returned as part of the lookup can be used both
-            by local (e.g. servlet) and remote (e.g. RMI) clients -->
+            by local (e.g. servlet) and remote (e.g. RMI) clients 
+            ?? Doe the jndi stuff even work - Chris said something about it not working.
        <attribute name="JndiName">
            name=DefaultCache
            locatorURI=socket://:5555
        </attribute>
-
+	-->
         <!-- Configure the TransactionManager -->
         <attribute name="TransactionManagerLookupClass">org.jboss.cache.JBossTransactionManagerLookup</attribute>