You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Christopher Tubbs (JIRA)" <ji...@apache.org> on 2014/04/25 20:35:18 UTC
[jira] [Updated] (ACCUMULO-869) Determine best default classloader
hierarchy
[ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christopher Tubbs updated ACCUMULO-869:
---------------------------------------
Summary: Determine best default classloader hierarchy (was: Determine best default classloader hierarchy )
> 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: Keith Turner
> 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 was sent by Atlassian JIRA
(v6.2#6252)