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 490c230523f03a96ca5b3a7db4b4f94ca770d546..673aaceb6d5114f23ef4303fa7520b9224a1f936 100644 (file)
--- 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());
                 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));
         }
         for (Object key: props.keySet()) { 
             System.out.println("Key " + key + " value " + props.getProperty((String)key));
         }