You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2006/04/14 23:50:00 UTC

[jira] Created: (GERONIMO-1852) Configuration and Kernel may differ on what gbeans are installed

Configuration and Kernel may differ on what gbeans are installed
----------------------------------------------------------------

         Key: GERONIMO-1852
         URL: http://issues.apache.org/jira/browse/GERONIMO-1852
     Project: Geronimo
        Type: Bug
    Security: public (Regular issues) 
  Components: kernel  
    Versions: 1.1    
    Reporter: David Jencks
 Assigned to: Dain Sundstrom 
     Fix For: 1.1


A configuration always says it contains the gbeans that it was configured with (possibly adding more dynamically) and does not take into account the modifications (load='false" to remove, or added gbeans) from the local attribute store. This messes up attempts to resolve single valued references.

One possible solution would be to supply the attribute manager to the configuration constructor and let it mess with the gbeans right then and there.


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


[jira] Assigned: (GERONIMO-1852) Configuration and Kernel may differ on what gbeans are installed

Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1852?page=all ]

David Jencks reassigned GERONIMO-1852:
--------------------------------------

    Assign To: David Jencks  (was: Dain Sundstrom)

> Configuration and Kernel may differ on what gbeans are installed
> ----------------------------------------------------------------
>
>          Key: GERONIMO-1852
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1852
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: kernel
>     Versions: 1.1
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.1

>
> A configuration always says it contains the gbeans that it was configured with (possibly adding more dynamically) and does not take into account the modifications (load='false" to remove, or added gbeans) from the local attribute store. This messes up attempts to resolve single valued references.
> One possible solution would be to supply the attribute manager to the configuration constructor and let it mess with the gbeans right then and there.

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


[jira] Closed: (GERONIMO-1852) Configuration and Kernel may differ on what gbeans are installed

Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
     [ http://issues.apache.org/jira/browse/GERONIMO-1852?page=all ]
     
David Jencks closed GERONIMO-1852:
----------------------------------

    Resolution: Fixed

fixed in rev 394430 as per suggestion.

> Configuration and Kernel may differ on what gbeans are installed
> ----------------------------------------------------------------
>
>          Key: GERONIMO-1852
>          URL: http://issues.apache.org/jira/browse/GERONIMO-1852
>      Project: Geronimo
>         Type: Bug
>     Security: public(Regular issues) 
>   Components: kernel
>     Versions: 1.1
>     Reporter: David Jencks
>     Assignee: David Jencks
>      Fix For: 1.1

>
> A configuration always says it contains the gbeans that it was configured with (possibly adding more dynamically) and does not take into account the modifications (load='false" to remove, or added gbeans) from the local attribute store. This messes up attempts to resolve single valued references.
> One possible solution would be to supply the attribute manager to the configuration constructor and let it mess with the gbeans right then and there.

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