[MYFACES-2290] Add OSGi bundle information and bundle classloader / activator

• Type: New Feature
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 1.2.8-SNAPSHOT
• Fix Version/s: 2.0.5
• Component/s: General
• Environment: OSGi (Equinox, Apache Felix, ...)
• Assignee: Leonardo Uribe
• Reporter: Felix Röthenbacher
• Created: 15/Jul/09 02:50
• Updated: 04/Apr/11 21:45
• Resolved: 10/Mar/11 23:20

Description

The provided patch will add OSGi information to bundle manifest. A bundle activator class makes the MyFaces framework aware that it is running in a bundle environment. A bundle classloader is used to load classes and resources from the bundle classpath. The patch doesn't require any new runtime dependencies and doesn't affect class loading in a non-OSGi environment. Though, small modifications to classloading were needed. This was mainly replacing Thread.currentThread.getContextClassLoader() with ClassUtils methods.

To run MyFaces in an OSGi environment both bundles (myfaces-api and myfaces-impl) have to be started in the OSGi container. Additionally, the myfaces-impl bundle has to be made available to myfaces-api. Use a fragment bundle with myfaces-api as Fragment-Host and myfaces-impl as Required-Bundle.

Issue Links

• blocks: GERONIMO-4996 myfaces 2 osgi integration
• incorporates: MYFACES-1878 DigesterFacesConfigUnmarshallerImpl uses context classloader rather than MyFaces ClassLoader
• incorporates: MYFACES-1885 OSGi and web.xml parsing
• incorporates: MYFACES-2442 Problem when using MyFaces with Spring DM within an OSGi environment
• incorporates: MYFACES-2550 AnnotationConfigurator and scanning of myfaces impl jar
• incorporates: MYFACES-2995 Make method of determinine app context in FactoryFinder pluggable
• is related to: MYFACES-1158 Use of context classloader as key in _registeredFactoryNames