You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@avalon.apache.org by "Niclas Hedhman (JIRA)" <de...@avalon.apache.org> on 2004/11/13 03:12:26 UTC

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

     [ http://nagoya.apache.org/jira/browse/RUNTIME-34?page=history ]
     
Niclas Hedhman closed RUNTIME-34:
---------------------------------


> Aggregation characteristics under composite components.
> -------------------------------------------------------
>
>          Key: RUNTIME-34
>          URL: http://nagoya.apache.org/jira/browse/RUNTIME-34
>      Project: Merlin Runtime
>         Type: Bug
>   Components: ACTIVATION
>     Versions: 3.3.0
>     Reporter: Stephen McConnell
>     Assignee: Stephen McConnell
>      Fix For: 3.4.0

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

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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