Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <4774182.1146631067859.JavaMail.jira@brutus>
Date: Wed, 3 May 2006 04:37:47 +0000 (GMT+00:00)
From: "Dain Sundstrom (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Closed: (GERONIMO-1931) Deployers and the deploying classes
 are in separate class loader hierarchies
In-Reply-To: <22498755.1146172838355.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/GERONIMO-1931?page=all ]
     
Dain Sundstrom closed GERONIMO-1931:
------------------------------------

    Fix Version: 1.1
                     (was: 1.2)
     Resolution: Fixed

Fixed. You can now remove the lame reflection work around.

> Deployers and the deploying classes are in separate class loader hierarchies
> ----------------------------------------------------------------------------
>
>          Key: GERONIMO-1931
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1931
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: deployment
>     Versions: 1.1
>     Reporter: Dain Sundstrom
>     Assignee: Dain Sundstrom
>      Fix For: 1.1

>
> The deployers are loaded from the main KernelConfiguraitonManager, where as when we deploy the new deployments are loaded from a private SimpleConfigurationManager.  This means two classloaders are completely separate and deployers see different versions of the spec classes.  Therefor, the deployers can't make use of instanceof and can use code like this:
> TimedObject.class.inAssignable(beanClass)
> This makes deployers unnecessarily complex and error prone.  This can easily be addressed by having the private SimpleConfigurationManager in the DeploymentContext first check main KernelConfigurationManager to see if the configuration exists before reloading it from disk.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira