From: erik <erik@77661180-640e-0410-b3a8-9f9b13e6d0e0>
Date: Wed, 14 May 2008 21:11:35 +0000 (+0000)
Subject: SpringComponent now supports adding properties as beans instead of
X-Git-Tag: wamblee-utils-0.2~1^2~123
X-Git-Url: http://wamblee.org/gitweb/?a=commitdiff_plain;h=392eabdb33253689a20fc67cb77a4d53366fd072;p=utils

SpringComponent now supports adding properties as beans instead of
through property configurer.

HibernateComponent no longer reads the hibernate properties.
Next step is to put in generic hibernate properties through the constructor and to put in application-independent properties
(schemaupdate and dialect) through a hibernate config object as a required interface.
---

diff --git a/security/src/test/java/org/wamblee/usermgt/hibernate/ExternalDatasourceComponent.java b/security/src/test/java/org/wamblee/usermgt/hibernate/ExternalDatasourceComponent.java
index 490c2305..673aaceb 100644
--- a/security/src/test/java/org/wamblee/usermgt/hibernate/ExternalDatasourceComponent.java
+++ b/security/src/test/java/org/wamblee/usermgt/hibernate/ExternalDatasourceComponent.java
@@ -40,6 +40,7 @@ public class ExternalDatasourceComponent extends SpringComponent {
                 createProvidedMap(), new TreeMap<RequiredInterface, String>());
         Properties props = new Properties(); 
         props.load(new ClassPathResource(DATABASE_PROPERTIES).getInputStream());
+     
         for (Object key: props.keySet()) { 
             System.out.println("Key " + key + " value " + props.getProperty((String)key));
         }