| commit | 0c7a1a1f5c25b14823d3daecaefbcc1463901098 | |
| author | Atsushi Eno <atsushi@ximian.com> | |
| Wed, 29 Sep 2010 07:41:59 +0000 (29 16:41 +0900) | ||
| committer | Atsushi Eno <atsushi@ximian.com> | |
| Wed, 29 Sep 2010 07:41:59 +0000 (29 16:41 +0900) | ||
| tree | 0b1dc571fefc78ca3811f793155d064387838424 | treesnapshot (tar.gz zip) |
| parent | 957abaee41d4a8a6cb98471c159ae79001edf0fc | commitdiff |
Fix the issue that callback contract often gets confused by picking unexpected contract type.
The problem is that DispatchRuntime.Type is a service implementation type
that could implement two or more contract interfaces, and it was in random
order how ServiceProxyGenerator picks up the contract type. Now it looks
for correct contract type instead of the service type by exactly looking
for the target contract in the endpoint (dispatcher).
The problem is that DispatchRuntime.Type is a service implementation type
that could implement two or more contract interfaces, and it was in random
order how ServiceProxyGenerator picks up the contract type. Now it looks
for correct contract type instead of the service type by exactly looking
for the target contract in the endpoint (dispatcher).