Type: Technical Task
Affects Version/s: None
Fix Version/s: 7.0.0 M7
The new approach for our Service Builder based applications will allow the end user to define dependencies on regular OSGi services.
In order to do that, we are putting in place a new mechanism were these dependencies will be handled by the new infrastructure in order to create and destroy the Spring context in a nice manner.
How does the plugin work?
- You just need to define in your application which annotation is going to be used to define your Service dependencies. For example, in the portal, we will be writing:
The previous snippet means that all the beans created within our application contexts which has a field with this annotation will be processed, and this classes will be used as dependencies that will be need to be satisfied before creating the final context
In addition to that, you will be able to define dependencies in the file
using the following format
For example, if you want to express a dependency on a service of type bar.foo.Foo you will need to write something like