[
http://jira.qos.ch/browse/LBCLASSIC-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ceki Gulcu closed LBCLASSIC-30.
-------------------------------
> Make ContextSelectors truely pluggable/configurable
> ---------------------------------------------------
>
> Key: LBCLASSIC-30
> URL: http://jira.qos.ch/browse/LBCLASSIC-30
> Project: logback-classic
> Issue Type: Bug
> Components: Other
> Affects Versions: unspecified
> Environment: Operating System: Windows
> Platform: PC
> Reporter: Lars Ködderitzsch
> Assignee: Logback dev list
> Fix For: 0.9.14
>
>
> Currently the ContextSelectors in Logback are limited to Default and JNDI,
> whereas a system property leads to ContextJNDISelector being pulled.
> This stuff is all hardcoded therefore not configurable.
> I cannot use ContextJNDISelector because of a bug(?) in Websphere 6.1. In WS
> 6.1. env-entry values are seemingly bound to the JNDI at a very late point.
> This leads to that the JNDI lookups fail because Logback initializes (through
> jlc-over-sl4j) way earlier in the application startup phase.
> It boils down to that I cannot use ContextJNDISelector in WS 6.1.
> For this reason I wanted to provide a custom ContextSelector to Logback,
> which is currently not possible.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
logback-dev mailing list
[email protected]
http://qos.ch/mailman/listinfo/logback-dev
