From d67a117843d23eaf7b44f5c048d3fdee9310b2a1 Mon Sep 17 00:00:00 2001 From: Erik Brakkee Date: Wed, 14 May 2008 21:11:35 +0000 Subject: [PATCH 1/1] 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. --- .../wamblee/usermgt/hibernate/ExternalDatasourceComponent.java | 1 + 1 file changed, 1 insertion(+) 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()); 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)); } -- 2.31.1