Ok, great, thanks Chetan for clarifying, then it seems ConfigurationFactory is
the right fit for my use case :)
Regards,
Tommaso
On 12/set/2013, at 06:16, Chetan Mehrotra wrote:
Hi Tommaso,
In general you should always use the ConfigurationFactory approach as
it is lot more simpler and
Hi
Am 11.09.2013 um 15:36 schrieb Tommaso Teofili:
Thanks a lot Chetan, that helps a lot!
In the mentioned link it seems both ConfigurationFactory and
ManagedServiceFactory could be used for that purpose, do you know if there is
any difference / advantage / disadvantage of using one
On 12/set/2013, at 08:35, Felix Meschberger wrote:
Hi
Am 11.09.2013 um 15:36 schrieb Tommaso Teofili:
Thanks a lot Chetan, that helps a lot!
In the mentioned link it seems both ConfigurationFactory and
ManagedServiceFactory could be used for that purpose, do you know if there
is
Hi all,
that's probably a trivial question but I'm looking for the best practice to
create and register OSGi Services from configurations.
Here's an example scenario:
- I have an interface FooBar
- I have an implementation DefaultFooBarImpl
- I want to be able to specify a node like:
{
You can use Component based on ConfigurationFactory. Have a look at
[1] for one such example
[1] http://stackoverflow.com/a/15872131/1035417
Chetan Mehrotra
On Wed, Sep 11, 2013 at 3:05 PM, Tommaso Teofili teof...@adobe.com wrote:
Hi all,
that's probably a trivial question but I'm looking
Thanks a lot Chetan, that helps a lot!
In the mentioned link it seems both ConfigurationFactory and
ManagedServiceFactory could be used for that purpose, do you know if there is
any difference / advantage / disadvantage of using one instead of the other?
Regards,
Tommaso
On 11/set/2013, at
Hi Tommaso,
In general you should always use the ConfigurationFactory approach as
it is lot more simpler and easy to use.
ManagedServiceFactory is useful in few cases when you do not want your
bundle to depend on any other service runtime apart from core OSGi
framework. So suitable for
