e4 – Dependency and Service Lookup Tooling

Today I extended my current implementation a bit so that I now extract the currently injected fields in a class and display them in the dialog one can open from within the JavaEditor. The following videos present shows this in action.

The next step is to add injected services through the Dialog. People asked in comments of the last post whether this support is isolated to e4 and it’s services and the answer is no. The current implementation simply registers a service in the OSGi-ServiceRegistry.

public interface IDIServiceRegistry {
  public void addServiceProvider(IDIServiceProvider descriptor);
  public void removeServiceProvider(IDIServiceProvider descriptor);
  public List<IDIServiceProvider> getProviders();

Potential Tool implementors can use and provide informations about available services who are probably available at runtime. As an example implementation I’ve implemented 2 example bundles who contribute providers for e4-core services using DS (you see in the screencast that no available services are there until the tooling bundles are started).

The contribution of the Logger-Service is done looks like this:

public class LoggerProvider extends DIServiceProvider implements IDIServiceProvider {
  public LoggerProvider() {
    System.err.println("Instance created");

  public String getLabel() {
    return "Logger Service";

  public String getDescription() {
    return "Logging warnings, errors, information, as well as capturing debug and trace information. Everything done through this interface is not meant for normal end users. Strings are not expected to be translated.";

  public String getServiceClassName() {
    return "org.eclipse.e4.core.services.Logger";

  public String getBundle() {
    return "org.eclipse.e4.core.services";

  public String getProduct() {
    return "e4";

  public String getCategory() {
    return "Core Services";

and contributed like this using DS:

<?xml version="1.0" encoding="UTF-8"?>
      <provide interface="org.eclipse.e4.ui.jdt.IDIServiceProvider"/>

After having implemented the Class-Modification. I think the next logic step would be to write some PDE-Addon which simply registers all available DS-Services found in the Target-Platform into the DI-Registry. I’m still in an experimental stage so probably this is all crap and one has to address the problem differently.

Anyways I’ve learned something about IJavaProject and the AST-Stuff coming with JDT and it’s been a lot of fun so far.

This entry was posted in e4. Bookmark the permalink.

5 Responses to e4 – Dependency and Service Lookup Tooling

  1. Salva says:

    Hmmm – Dialogs bite. 🙂 Why isn’t this a View?

  2. ekkescorner says:

    great ! … first steps into the direction of DS tooling 🙂

  3. Tonny Madsen says:

    This would be a starting point, but… it does not really help with the cases, where I believe DI really sucks: ContextInjectionFactory.invoke and friends…

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.