From: erik <erik@77661180-640e-0410-b3a8-9f9b13e6d0e0>
Date: Thu, 15 May 2008 21:22:02 +0000 (+0000)
Subject: added databasecomponent and now using Derby in the unit tests.
X-Git-Tag: wamblee-utils-0.2~1^2~109
X-Git-Url: http://wamblee.org/gitweb/?a=commitdiff_plain;h=38e4acb4946a06856a98477c597d0a5f80c36df5;p=utils

added databasecomponent and now using Derby in the unit tests.
As a result, no external Mysql database must be setup before running
the unit tests. It is now checkout and go!!
---

diff --git a/system/spring/src/main/java/org/wamblee/system/spring/component/HibernateComponent.java b/system/spring/src/main/java/org/wamblee/system/spring/component/HibernateComponent.java
index 6f5c0a95..4b256254 100644
--- a/system/spring/src/main/java/org/wamblee/system/spring/component/HibernateComponent.java
+++ b/system/spring/src/main/java/org/wamblee/system/spring/component/HibernateComponent.java
@@ -73,7 +73,7 @@ public class HibernateComponent extends SpringComponent {
                 return DerbyDialect.class.getName(); 
             }
         });
-        getHibernateProperties().put(HIBERNATE_DIALECT_PROP, MySQLInnoDBDialect.class.getName());
+        getHibernateProperties().put(HIBERNATE_DIALECT_PROP, dialect);
         
         
         return super.doStart(aExternalScope);