Going forward, how to handle extensions in a pure e4 app? [message #760669] |
Sat, 03 December 2011 23:19  |
Eclipse User |
|
|
|
In 3.x I understand how to define extension points and contribute
extensions to those points. What I feel I am missing is what is the
model for how to handle this in a pure e4 way? IIRC, defining
extensions the 3.x way will force the use of the compatibility layer.
ATM I don't have a real issue with that, however I still would like to
understand what should be done if you want to go pure e4.
Wb
|
|
|
|
|
Re: Going forward, how to handle extensions in a pure e4 app? [message #761106 is a reply to message #760705] |
Mon, 05 December 2011 17:50  |
Eclipse User |
|
|
|
There are at least 3 ways to provide extensions:
- Extension points
- Services (Declarative and registered)
- DI with the IEclipseContext and IContextFunctions
They differ in terms of ease-of-definition, the obliviousness of the code using the extension, the types of things that can be injected (like data, as you mentioned), and lifecycle. And in other ways too.
Brian.
|
|
|
Powered by
FUDForum. Page generated in 0.04131 seconds