|E4 Tools Internationalization - Use case on OSGi Level [message #1067764]
||Wed, 10 July 2013 13:37
| Christoph Keimel
Registered: December 2010
Hi Dirk! Hi Tom!|
I am currently testing your new internationalization mechanism from e4 tools by migration a small e4 application. In this project all the messages are externalized like discribed in your blog: All the messages were externalized into one large Messages class, that is used by all other classes of the application.
I changed the Messages class as described and started to refactor all the accesssing classes. This is where I am running into a problem: Some of the classes are OSGi service implementations, so they actually aren't hooked into E4 DI.
Is the Translation available as an OSGi service, which I could use as a dependency in DS?
Is there a way for an OSGi service implementation to know, when the translation service is available in the context?
Powered by FUDForum
. Page generated in 0.04755 seconds