Ceki has this behavior been intentionally changed between 1.2 and 1.4?
BR,
Richard
On 6/21/2023 2:35:36 PM, Richard Sand <rs...@idfconnect.com> wrote:
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
[431881a4-a923-4738-a6fe-3a9eece779d9]_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
https://mailman.qos.ch/cgi-bin/mailman/listinfo/logback-dev
