geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dain Sundstrom (JIRA)" <...@geronimo.apache.org>
Subject [jira] Commented: (GERONIMO-1931) Deployers and the deploying classes are in separate class loader hierarchies
Date Sat, 29 Apr 2006 04:40:39 GMT
    [ http://issues.apache.org/jira/browse/GERONIMO-1931?page=comments#action_12377065 ] 

Dain Sundstrom commented on GERONIMO-1931:
------------------------------------------

The deployment context creates a private SimpleConfigurationManager.  I believe that we need
a sub-class of SimpleConfigurationManager that gets the main geronimo ConfiguationManager
as an argument.  Then any time we are checkin if a configuration exists, we first check the
main geronimo ConfigurationManager.  This will cause the new private configuration manager
to see all currently loaded configurations in the server, and since the deployer is clearly
already loaded it will see the same classes as the deployer.

> 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
>      Fix For: 1.2

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


Mime
View raw message