sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rohit Kumar (JIRA)" <j...@apache.org>
Subject [jira] [Created] (SLING-3370) Bootdelegation support for third party library
Date Tue, 04 Feb 2014 17:10:09 GMT
Rohit Kumar created SLING-3370:
----------------------------------

             Summary: Bootdelegation support for third party library
                 Key: SLING-3370
                 URL: https://issues.apache.org/jira/browse/SLING-3370
             Project: Sling
          Issue Type: Improvement
          Components: Launchpad
    Affects Versions: Launchpad Base 2.5.0
            Reporter: Rohit Kumar


Requirement:
1) Bootdelegate third party library in SLing OSGI framework.
2) Bootdelegated classes and resources should be looked up from configured third party jars
only. Similar classes from parent classloaders should not leak into system. This case arises
usually in Web deployment scenario. 

Infact we want to bootdelegate RSA library and at the same time prevent interference from
parent classloaders in Web deployment model.

Approach:

1) We extend SlingLauncherClassloader to scan a predefined path (say <launchpadhome>/lib/etx)
for jar files and add them to its classpath. This is done at startup. SlingLauncherClassloader
will  try to load class from its classpath before trying parent classloaders. Currently it
is done for org.apache.sling.launchpad.base.jar.  
2) The packages can be configured for bootdelegation using sling properties:
	sling.bootdelegation.class.<any bootdelegated class>=<bootdelegated package>



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message