Community
Participate
Working Groups
IProxyResolverService is the new API that probably should replace ProxyHelper. But where as ProxyHelper/EcoreIndex is explicitely called via API when proxy resolution is finished, there is no such API in IProxyResolverService. That means, that any data structures built for proxy resolving will have no chance of being tore down, resulting in a memory leak. Is that intended? I assume that this is intended for a specific modeling service implementation, but expect this to be too limited for the genereal case. What is the expected use?
Closed stale issue before migration