A typical use-case: I'm having applicationContext.xml
and dispatcher-servlet.xml
. In the parent context (applicationContext.xml
) I have:
<context:property-placeholder location="classpath:application.properties" />
However, the properties loaded by it are not accessible to the web context - neither in xml, nor using @Value
. (They are just not resolved and the expression (${varName}
) is set as value instead)
I worked it around by adding the <context:property-placeholder>
to dispatcher-servlet.xml
as well, but I wondered whether:
- This is expected behaviour
- There isn't a better way to expose the properties to the child context.
See Question&Answers more detail:
os 与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…