[CXF-2893] CXF should use class' classloader for initialization of its loggers

• Type: Bug
• Status: Closed
• Priority: Trivial
• Resolution: Fixed
• Affects Version/s: 2.2.9
• Fix Version/s: 2.2.10
• Assignee: Daniel Kulp
• Reporter: Hynek Mlnarik
• Created: 14/Jul/10 07:29
• Updated: 11/Oct/10 14:52
• Resolved: 16/Jul/10 17:59

Description

The class org.apache.cxf.common.logging.LogUtils should attempt to use plain Class.forName(cname) if Class.forName(cname, true, Thread.currentThread().getContextClassLoader()) fails.

Rationale: Current thread might not be able to access cxf classes. Take as an example the following OSGi bundles:
1) bundle with a http server.
2) bundle with CXF-based servlet SomeCXFServlet. The bundle contains CXF as private OSGi library.
A servlet SomeCXFServlet from bundle (2) has access to CXF via SomeCXFServlet.class.getClassloader(), similarly LogUtils class via its classloader. However, the servlet initialization is performed from http server thread that does not have access to bundle (2) private classes. Initialization of a logger is hence also made from the http thread. CXF tries to load its org.apache.cxf.common.logging.*Logger classes - the attempt however fails because the current thread's classloader is used instead of the LogUtils'.

Solution: Try to load the class using Class.forName(cname) if Class.forName(cname, true, Thread.currentThread().getContextClassLoader()) fails.

Will attach diff in a separate comment