geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gianny Damour (JIRA)" <j...@apache.org>
Subject [jira] Updated: (GERONIMO-4590) One ClassLoader per Jar Model
Date Tue, 17 Mar 2009 10:56:50 GMT

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

Gianny Damour updated GERONIMO-4590:
------------------------------------

    Attachment: additional-maven-dependencies.jar
                OneClassLoaderPerJar.txt

OneClassLoaderPerJar.txt is a geronimo-kernel patch.

additional-maven-dependencies.jar is a jar to be unpacked in the geronimo repository, which
include additional maven dependency declarations for specific JAR.

> One ClassLoader per Jar Model
> -----------------------------
>
>                 Key: GERONIMO-4590
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4590
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: kernel
>    Affects Versions: 2.1.3
>            Reporter: Gianny Damour
>            Assignee: Gianny Damour
>         Attachments: additional-maven-dependencies.jar, OneClassLoaderPerJar.txt
>
>
> As discussed on @dev, to reduce the number of ClassCastExceptions caused by collaborating
configurations importing the same dependencies, the classloading design can be improved to
use a shared and global poll of classloaders.
> Each classloader in this global poll is mapped to only one JAR. They are put in a hierarchy
according to their maven dependency declarations. As maven dependencies may not be systematically
correct, additional dependency declarations can also be provided by dropping a XML file "artifactId-version-additional.xml"
beside the JAR or POM file "artifactId-version.jar (.pom)" whose dependencies are to be supplemented.
> This patch is a preview of the functionality to trigger more discussions.
> 22 out of the 74 configurations of the jetty-jee5 assembly can start fine with this patch.
The failure observed for the failing configuration appears to be another maven dependency
declaration issue.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message