[jboss-cvs] JBossAS SVN: r99714 - projects/docs/enterprise/EWP_5.0/Hibernate/Hibernate_Core/en-US.

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

Author: laubai
Date: 2010-01-21 01:52:05 -0500 (Thu, 21 Jan 2010)
New Revision: 99714

Modified:
   projects/docs/enterprise/EWP_5.0/Hibernate/Hibernate_Core/en-US/best_practices.xml
Log:
Removed error in best practices; help from stliu.

Modified: projects/docs/enterprise/EWP_5.0/Hibernate/Hibernate_Core/en-US/best_practices.xml
===================================================================
--- projects/docs/enterprise/EWP_5.0/Hibernate/Hibernate_Core/en-US/best_practices.xml	2010-01-21 06:38:02 UTC (rev 99713)
+++ projects/docs/enterprise/EWP_5.0/Hibernate/Hibernate_Core/en-US/best_practices.xml	2010-01-21 06:52:05 UTC (rev 99714)
@@ -125,7 +125,7 @@
                     In performance-critical areas of the system, some kinds of operations might benefit from 
                     direct JDBC. Do not assume, however, that JDBC is necessarily faster. Please wait until you <emphasis>know</emphasis> something is a bottleneck. 
                     If you need to use direct JDBC, 
-                    you can open a Hibernate <literal>Session</literal> and usingfile:///usr/share/doc/HTML/en-US/index.html that JDBC connection. This 
+                    you can open a Hibernate Session and wrap your JDBC operation as a Work object with <methodname>session.doWork(Work)</methodname>. This 
                     way you can still use the same transaction strategy and underlying connection provider.
                 </para>
             </listitem>