[e4-dev] Accessing configuration choices in deeplinking code

[David Orme <djo@xxxxxxxxxxxxxxxxxxxxxxxxx>]

Hi all,

As I mentioned on last week's call, it's nice to have our stuff in CVS and I just got word from the EMO that the IP team has approved our contribution.  (Woo hoo!)

Before we get into the build, we have one final technical issue to work out and I'd like peoples' advice on how to solve this.  The question is the following:

Deeplinking has configuration that it needs to access.  As I understand it, the E4 way would be to use the E4 DI plugin.  

But I'm concerned with using the E4 DI plugin since Eclipse isn't the only downstream consumer of our code and we have to ship on 3.4 until at least 3.6.2.

I'd like advice here.  I would prefer to migrate away from our metaconfig plugin toward the E4 DI plugin, but am not sure what is the best way to do that....  Perhaps exposing a java.util.Properties object as an OSGI service would be a good middle ground since (correct me if I'm wrong), OSGI services can be injected using E4 DI, which would give us a migration path going forward.


Thanks in advance for peoples' thoughts/advance/suggestions.


Dave Orme