Missing system property placeholder resolving in orcl:pooling-data-source [DATAJDBC-45]

[spring-projects-issues]

Jan Philipp opened DATAJDBC-45 and commented

After I'd found Spring Data JDBC/Oracle by surprise, I want give it a try.

I've tried following

<orcl:pooling-datasource id="dataSource" properties-location="file:${user.home}aFileInMyHomeDir.properties" />

Just like other setups (i.e. MessageSource), but this one will not work. Stepping into it resolves that ResourceLoader.getResource() will be invoked with file:${user.home}aFileInMyHomeDir.properties (not replaced) and cannot itself resolve the property.

I would say this is a bug or a missing resolving.. or did I have missed something? How can I provide database properties without a) my classpath and b) without specifying an absolute path which isn't possible when supporting multiple platforms (win/*nix).

A fallback could be defining separated connection and cache properties, however, referenced properties beans are not allowed for connection-properties and connection-cache-properties

---

Affects: Ext 1.0 RELEASE

Referenced from: commits spring-attic/spring-data-jdbc-ext@1966c38

[spring-projects-issues]

Thomas Risberg commented

It probably doesn't resolve the expression - I'll take a look and add full SPEL support for the next maintenance release

[spring-projects-issues]

Thomas Risberg commented

Added resolution of system properties for property file locations