Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Won't Fix
-
3.3.0
-
None
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.