You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by ji...@apache.org on 2004/05/07 03:37:56 UTC

[jira] Updated: (RUNTIME-2) Separation of facilities from component containers.

The following issue has been updated:

    Updater: Stephen McConnell (mailto:mcconnell@apache.org)
       Date: Thu, 6 May 2004 6:37 PM
    Changes:
             type changed from New Feature to Improvement
             summary changed from Separation of facilities from components. to Separation of facilities from component containers.
             Version changed to 3.3
             Component changed to Composition
             Fix Version changed to 4.0
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/RUNTIME-2?page=history

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/RUNTIME-2

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: RUNTIME-2
    Summary: Separation of facilities from component containers.
       Type: Improvement

     Status: Open
   Priority: Major

    Project: Merlin Runtime Platform
 Components: 
             Composition
   Fix Fors:
             4.0
   Versions:
             3.3

   Assignee: Stephen McConnell
   Reporter: Stephen McConnell

    Created: Wed, 5 May 2004 5:49 AM
    Updated: Thu, 6 May 2004 6:37 PM

Description:
Providing a mechanism to seperate facilities from components at the container specification level is desirable.  

This would ensure:

  (a) clear separation of facility dependencies
      from component dependencies

  (b) elimination of the exposure of the compositon
      api and spi from regual components

Achiving the above would require some additional classloader management - in particular, delegation from a container facilities classloader to a parent container's facilities classloader.

In addition - we would need to include a mechanisms for a component to declare the assumptions it has concerning facilities.


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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