accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-869) Determine best default classloader hierarchy
Date Fri, 21 Dec 2012 21:49:12 GMT

    [ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538448#comment-13538448
] 

Keith Turner commented on ACCUMULO-869:
---------------------------------------

Looking into this, I think what we want instead of isolation (a very sparse parent classloader)
is class loader that does not delegate to the parent unless it does not have the class.

http://tech.puredanger.com/2006/11/09/classloader/
                
> Determine best default classloader hierarchy 
> ---------------------------------------------
>
>                 Key: ACCUMULO-869
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-869
>             Project: Accumulo
>          Issue Type: Sub-task
>          Components: start
>            Reporter: Keith Turner
>            Assignee: Dave Marion
>             Fix For: 1.5.0
>
>         Attachments: ACCUMULO-869-1.patch
>
>
> A user created context classloader in the current patch does not have the system context
as it parent.  If the system context contained Accumulo jars, then the user context would
have to add its own Accumulo jars.  The drawback of this is that the user context may use
a different version of accumulo jars than the system context leading to unexpected behavior.
  The advantage of this is that user context could load newer jars.  For example, if Accumulo
depended on an old json library the user context could load a newer version with no problems.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message