I want to configure some bean properties using org.springframework.beans.factory.config.PropertyP laceholderConfigurer, but the configuration (currently loaded as applicationContext) is itself located in a JAR on EAR level, and the .properties file to load by the org.springframework.beans.factory.config.PropertyP laceholderConfigurer *MUST* be located in some "expanded" place in the EAR to grant easy access to operations / deployers. (It is because they must setup some values for production in this file which I am not allowed to know in detail as a developer.)
The EAR contains 3 WARs, 7 EJB-JARS and some "normal" JARs, is deployed on WAS60 and as such the WARs are guaranteed to be expanded to the file system on deployment. The applicationContext is actually located in one of the "normal" JARs on EAR level, and it is used only by logic residing in the WARs (not in any EJB).
Is there some way to point to an "expanded" location inside the EAR from inside my applicationContext?
Or is it required for any applicationContext which wants to load some resource from the file system (relative to the EAR, not knowing about its absolute location) also to reside in an "expanded" location like an expanded WAR?