[MYFACES-1158] Use of context classloader as key in _registeredFactoryNames

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 1.1.1
• Component/s: General
• Environment: Any
• Assignee: Leonardo Uribe
• Reporter: Toh Kim Huat
• Created: 01/Mar/06 12:47
• Updated: 21/Feb/11 18:50
• Resolved: 21/Feb/11 18:50

Description

In FactoryFinder.java, the context classloader is used as the key to set/retrieve the factoryClassNames Map from the _registeredFactoryNames map. Problems will occur if the context classloader used to put a factoryClassNames into the factoryClassNames Map is different from the context classloader used to retrieve a factoryClassNames from the factoryClassNames Map. The context classloader might be different if for instance the application uses a custom classloader which is inserted into the classloader hierarchy by setting the current context classloader as its parent classloader and then setting itself to be the current thread's context classloader.

Is it possible not to use the context classloader as the Map's key? Or perhaps if an entry cannot be retrieved from the Map using the current context classloader, can we use its parent (iteratively) to retrieve from the Map until we get an entry?

Issue Links

• is related to: MYFACES-2995 Make method of determinine app context in FactoryFinder pluggable
• relates to: MYFACES-2290 Add OSGi bundle information and bundle classloader / activator