[LOG4J2-513] Use more OSGi-friendly class loading mechanisms.

• Type: Sub-task
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.0-rc1
• Component/s: API
• Labels: api bundle classloader osgi

Environment

OSGi

• Assignee: Matt Sicker
• Reporter: Matt Sicker
• Created: 26/Jan/14 02:00
• Updated: 26/Apr/14 23:22
• Resolved: 26/Apr/14 23:22

Description

See for instance here. 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.

Issue Links

• is superceded by: LOG4J2-614 Log4j API should allow specifying a LoggerContextFactory at runtime.
• relates to: LOG4J2-373 Classloader issue in OSGi-environment