tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ben Sommerville (JIRA)" <tapestry-...@jakarta.apache.org>
Subject [jira] Updated: (TAPESTRY-1316) ClassFactoryClassPool doesn't cope with ClassLoaders that have a tree structure.
Date Mon, 05 Mar 2007 03:30:50 GMT

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

Ben Sommerville updated TAPESTRY-1316:
--------------------------------------

    Attachment: TAP-1316.patch

Patch to copy with classloaders with tree structures.

What it does is track the leaf classloader of each branch in the tree (that we have seen).
 When a new classloader is added we check to see if it is a child of an existing leaf.  If
so we replace the existing leaf.  If not we add a new leaf.

I have tested this under JBoss & it fixed the problem that I was having.  It hasn't been
tested under any other container.

> ClassFactoryClassPool doesn't cope with ClassLoaders that have a tree structure.
> --------------------------------------------------------------------------------
>
>                 Key: TAPESTRY-1316
>                 URL: https://issues.apache.org/jira/browse/TAPESTRY-1316
>             Project: Tapestry
>          Issue Type: Bug
>          Components: IoC Container
>    Affects Versions: 5.0.3
>            Reporter: Ben Sommerville
>         Attachments: TAP-1316.patch
>
>
> As per the comment on addClassLoader, if the class loader hierarchy is not a flat line
then the classloaders can be lost.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tapestry.apache.org
For additional commands, e-mail: dev-help@tapestry.apache.org


Mime
View raw message