[jboss-jira] [JBoss JIRA] Commented: (JBCL-119) DependencyInfo.removeDependsOnMe never called

[Ales Justin (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBCL-119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12486418#action_12486418 ] 

Ales Justin commented on JBCL-119:
----------------------------------

I added few more checks for null.
We currently ignore them if null - keeping the same behavior as before.

But in the long run we need a better removal mechanism.

> DependencyInfo.removeDependsOnMe never called
> ---------------------------------------------
>
>                 Key: JBCL-119
>                 URL: https://jira.jboss.org/jira/browse/JBCL-119
>             Project: JBoss ClassLoader
>          Issue Type: Bug
>          Components: Dependencies
>            Reporter: Thomas Diesler
>            Assignee: Thomas Diesler
>             Fix For: JBossCL.2.0.7.GA
>
>
> Consider this
> BundleA
>   exports A
> BundleB
>   imports A
> #1 install BundleA
> #2 install/start BundleB
> #3 uninstall BundleB
> The DependencyInfo of BundleA holds a dependsOnMe entry for BundleB that is never removed.
> This contributes to the memory leak that we see in [JBOSGI-155]

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