[teiid-commits] teiid SVN: r4351 - tags/teiid-parent-8.1.0.Final/build/kits/jboss-as7/docs/teiid.

[teiid-commits at lists.jboss.org]

Author: shawkins
Date: 2012-08-21 06:50:28 -0400 (Tue, 21 Aug 2012)
New Revision: 4351

Modified:
   tags/teiid-parent-8.1.0.Final/build/kits/jboss-as7/docs/teiid/teiid-releasenotes.html
Log:
updating release notes

Modified: tags/teiid-parent-8.1.0.Final/build/kits/jboss-as7/docs/teiid/teiid-releasenotes.html
===================================================================
--- tags/teiid-parent-8.1.0.Final/build/kits/jboss-as7/docs/teiid/teiid-releasenotes.html	2012-08-21 10:35:47 UTC (rev 4350)
+++ tags/teiid-parent-8.1.0.Final/build/kits/jboss-as7/docs/teiid/teiid-releasenotes.html	2012-08-21 10:50:28 UTC (rev 4351)
@@ -150,14 +150,20 @@
 
 See the <a href="teiid-docs/teiid_admin_guide.pdf">Admin Guide</a> for more on configuration and installation.
 
-<h4>from 7.4</h4>
+<h4>from 8.0</h4>
 <ul>
-  <li>The configuration for the buffer service now defaults to 256/512 for processor and connector batch sizes respectively.  The buffer service also has 4 new properties inline-lobs, memory-buffer-space, memory-buffer-off-heap, and max-storage-object-size.  
-  If you were explicitly setting the value for 'max-reserve-kb', you should consider lowering that value to account for the memory buffer and/or explicitly set the memory-buffer-space. 
+  <li>teiid-security-users and teiid-security-roles properties files have been moved under the configuration directory of their respective deployment. 
 </ul>
 
+<h4>from 7.7</h4>
+<ul>
+  <li>The server is now dependent upon AS 7.x.  The old configuration and deployment structure is no longer applicable. 
+</ul>
+
 <h4>from 7.4</h4>
 <ul>
+  <li>The configuration for the buffer service now defaults to 256/512 for processor and connector batch sizes respectively.  The buffer service also has 4 new properties inline-lobs, memory-buffer-space, memory-buffer-off-heap, and max-storage-object-size.  
+  If you were explicitly setting the value for 'max-reserve-kb', you should consider lowering that value to account for the memory buffer and/or explicitly set the memory-buffer-space. 
   <LI>The configuration for authorization has been moved off of the RuntimeEngineDeployer bean and onto separate AuthorizationValidator and PolicyDecider beans.
   <LI>The configuration for the buffer manager has been simplified to refer to memory sizes in KB, rather than batch columns.
 </ul>