avalon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Niclas Hedhman (JIRA)" <...@avalon.apache.org>
Subject [jira] Resolved: (RUNTIME-34) Aggregation characteristics under composite components.
Date Sat, 13 Nov 2004 02:12:26 GMT
     [ http://nagoya.apache.org/jira/browse/RUNTIME-34?page=history ]
Niclas Hedhman resolved RUNTIME-34:

    Resolution: Won't Fix

Avalon is shutting down.
Come to the Metro project for further support. http://www.dpml.net

> 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:
If you want more information on JIRA, or have a bug to report see:

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

View raw message