Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 30 Nov 2012 02:11:58 +0000 (UTC)
From: "Dave Marion (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <1858032801.43622.1354241518757.JavaMail.jiratomcat@arcas>
In-Reply-To: <27635092.14542.1353537778354.JavaMail.jiratomcat@arcas>
Subject: [jira] [Assigned] (ACCUMULO-869) Determine best default classloader
 hierarchy
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/ACCUMULO-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dave Marion reassigned ACCUMULO-869:
------------------------------------

    Assignee: Dave Marion
    
> 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
>
>
> 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