| Standalone e4 RCP application, DI doesn't work [message #1063437] |
Thu, 13 June 2013 07:46  |
 Ozgur Cagdas
Messages: 32
Registered: May 2013 |
Member |
|
|
Hi,
I have an e4 RCP application which uses dependency injection and also depends on the Eclipse Framework. When I export the application as a standalone app, none of the injections happen (i.e. @PostContruct annotated methods are not called).
So, at first place, does the DI function on standalone apps? If yes, what am I missing here? Needless to say, it all works fine when compiled and launched within Eclipse.
Regarding the Eclipse Framework dependency, can I deploy a base Eclipse application together with my app, so it does satisfy dependencies through it? Actually, the Eclipse Framework dependency is at the simplest level, just using the IEclipseContext and couple of other simple structures, so no contribution to UI or use of any complex mechanisms.
Regards,
O.
[Updated on: Fri, 14 June 2013 08:34] Report message to a moderator |
|
|
| Re: Standalone e4 RCP application with DI [message #1063445 is a reply to message #1063437] |
Thu, 13 June 2013 08:15  |
Eclipse User |
|
|
|
|
Well it depends what you call framework but you only need what you have as dependencies on your .product file to have the app working. But yes e4 RCP is meant for standalone apps. It's an application framework for people to build upon. Your @PC not being called might be related to how you declare your dependency on javax.annotation.
|
|
|
|
Powered by
FUDForum. Page generated in 0.03015 seconds
] 
Search
Help
Register
Login
Home
