You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by de...@avalon.apache.org on 2004/07/09 20:17:19 UTC

[jira] Updated: (RUNTIME-34) Aggregation characteristics under composite components.

The following issue has been updated:

    Updater: Stephen McConnell (mailto:mcconnell@apache.org)
       Date: Fri, 9 Jul 2004 11:15 AM
    Changes:
             Fix Version changed to 3.4.0
             Fix Version changed from 4.0
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

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

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: RUNTIME-34
    Summary: Aggregation characteristics under composite components.
       Type: Bug

     Status: Open
   Priority: Major

    Project: Merlin Runtime
 Components: 
             ACTIVATION
   Fix Fors:
             3.4.0
   Versions:
             3.3.0

   Assignee: Stephen McConnell
   Reporter: Stephen McConnell

    Created: Fri, 11 Jun 2004 11:56 AM
    Updated: Fri, 9 Jul 2004 11:15 AM

Description:
Composite proxies are create as aggregates of the exported interfaces - in fact it would be better to construct a specific proxy corresponding to an identified service dependency. A side effect of aggregation is demonstrated in the following email thread where operations such as toString() that are shared across multiple provider components cannot be resolved in a predictable fashion.

http://marc.theaimsgroup.com/?t=108680644400026&r=1&w=2

The solution is to put in place a proxy linking a to the provider component only based on the dypendency resolution.


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