accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christopher Tubbs (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ACCUMULO-869) Determine best default classloader hierarchy
Date Fri, 25 Apr 2014 18:35:18 GMT

     [ 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)

Mime
View raw message