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...@codehaus.org on 2003/04/23 09:30:09 UTC

[jira] Created: (PNIX-47) BlockFactory

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=PNIX-47


Here is an overview of the issue:
---------------------------------------------------------------------
        Key: PNIX-47
    Summary: BlockFactory
       Type: New Feature

     Status: Unassigned
   Priority: Major

 Time Spent: Unknown
   Estimate: 0 minutes

    Project: phoenix
 Components: 
             Container Architecture
   Versions:
             4.1

   Assignee: 
   Reporter: Peter Donald

    Created: Wed, 23 Apr 2003 2:28 AM
    Updated: Wed, 23 Apr 2003 2:28 AM

Description:
Start Facilitating creation of Blocks through a Factory. Each component can optionally define a factory through which it is loaded. This will allow components to be created from arbitary locations. 

For example, it would be valid for the component to be specified using a rmi, corba, soap or other url. ie Something like

rmi://localhost/MyRemoteComponent

The factory would take this implementationKey and construct a component that obeys the avalon lifecycle contract and for all intents and purposes can be treated like a normal Avalon component.

These Factorys must be able to create the blocks themselves and the 
BlockBundle. The BlockBundle includes the BlockInfo object aswell as any associated descriptors (MXInfo files, schemas etc). 

The factory will look something like

interface BlockFactory
{
  Object createBlock( String implementationKey ) throws Exception;
  BlockBundle createBlockBundle( String implementationKey ) throws Exception;
}

interface BlockBundle
{
  BlockInfo getBlockInfo();
  InputStream getResourceAsStream(String);
}

The BlockFactory will pass through all Avalon lifecycle stages *except* Composable/Serviceable.

The initial implementions will allow at least RMI, AltRMI and Soap (via glue or axis?) objects to be dynamically assembled.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/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