[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [emf-dev] EMF interface instance access pattern
|
> one could imagine doing many things quite differently
Yes, the example below was just to initiate the discussion.
With the custom templates we can generate any code, and there is a
public API to "substitute" or "decorate" registries, validators and
mostly everything.
The question is a bit different: how would you do it today, with all the
power that OSGi and DI can give for it?
Regards,
AF
09.07.2019 16:02, Ed Merks пишет:
Those patterns appear in may places and others have complained:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=329209
Certainly with alternative service-based patterns and with things like
modern dependency injection frameworks, one could imagine doing many
things quite differently.
On 09.07.2019 11:27, Alexander Fedorov wrote:
Hello,
In EMF runtime and generated code there is a "interface instance
access" pattern like:
public interface Registry
{
public static final Registry INSTANCE = new RegistryImpl();
}
It is good and stable. It works perfect.
However, it may look "too static" for OSGi-based approach where
interface should not reference its implementation.
How would you implement it today for OSGi-oriented architecture
executed by 1.8+ Java?
Thanks,
AF
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/emf-dev
_______________________________________________
emf-dev mailing list
emf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/emf-dev
