Hi all,
Has anyone else encountered this issue with the change in when resolution of a
JNDI variable occurs? Or is there an alternative configuration that can still
achieve what was working in 1.2?
Basically I'm using a JNDI variable to define the path to a config file to
include:
<configuration scan="true">
<insertFromJNDI env-entry-name="java:comp/env/appHome" as="appHome" />
<include file="${appHome}/conf/logback-ssorest.xml"/>
</configuration>
The logback logs show:
11:12:45,716 |-INFO in ch.qos.logback.classic.LoggerContext[default] - This is
logback-classic version 1.4.6
11:12:45,776 |-INFO in
ch.qos.logback.core.joran.util.ConfigurationWatchListUtil@354c986c - Adding
file:/D:/IDFC/SSORest-3.1-casso/tomcat/bin/appHome_IS_UNDEFINED/conf/logback-ssorest.xml
to configuration watch list.
11:12:45,776 |-WARN in ch.qos.logback.core.joran.action.IncludeAction - Failed
to open
file:/D:/IDFC/SSORest-3.1-casso/tomcat/bin/appHome_IS_UNDEFINED/conf/logback-ssorest.xml
11:12:45,823 |-INFO in
ch.qos.logback.core.model.processor.InsertFromJNDIModelHandler - Setting
variable [appHome] to [../..] in [LOCAL] scope
Any thoughts?
BR,
Richard
[4f117000-5b64-40d3-9b49-7377c6a8c73d]_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
