[
https://issues.apache.org/jira/browse/LOG4J2-513?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matt Sicker reassigned LOG4J2-513:
----------------------------------
Assignee: Matt Sicker
> Use more OSGi-friendly class loading mechanisms.
> ------------------------------------------------
>
> Key: LOG4J2-513
> URL: https://issues.apache.org/jira/browse/LOG4J2-513
> Project: Log4j 2
> Issue Type: Sub-task
> Components: API
> Affects Versions: 2.0-rc1
> Environment: OSGi
> Reporter: Matt Sicker
> Assignee: Matt Sicker
> Labels: api, bundle, classloader, osgi
> Attachments: 0001-Fix-weird-usage-of-StatusLogger.patch,
> 0002-Refactor-class-loader-usage-in-LogManager.patch
>
>
> See for instance
> [here|http://njbartlett.name/2012/10/23/dreaded-thread-context-classloader.html].
> Currently, o.a.l.l.util.ProviderUtil has a findClassLoader() method that
> depends on using the thread context class loader (TCCL). Now this method may
> work in certain environments, but once you're in an OSGi environment, class
> loaders are far more modular thanks to each bundle getting its own class
> loader. The thread context class loader is oftentimes not the correct one in
> such an environment.
> I'll do more research on being compatible with OSGi without depending on
> OSGi. In the meantime, this ticket will have to do.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
