You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Marc Schaaf <ma...@marc-schaaf.de> on 2010/02/25 10:33:56 UTC
dOSGi: Change the startup of the DSW to Spring
Hi,
with regard to [1] I would like to change the startup of the dOSGi DSW
from a normal OSGi activator to Spring. This way the DSW would be
started by the Spring OSGi Extender bundles which would solve an issue
with the intent map loading. Currently the intent map is only
successfully loaded by the DSW if the Spring OSGi Extender was started
before.
Are there any objections against this approach ?
Thanks,
Marc
[1] http://issues.apache.org/jira/browse/DOSGI-66
Re: dOSGi: Change the startup of the DSW to Spring
Posted by Marc Schaaf <ma...@marc-schaaf.de>.
Thanks for the comments!
I agree with David, we already need spring for many other things.
However I would also like to have a non spring solution here but the
only other one that comes to my mind is to introduce some kind of lazy
loading mechanism for the intent map. This mechanism would than load it
as soon as spring is ready.
However I don't think that this is a better solution as this means that
from the perspective of a user the DSW is completely started but in the
background not all functionality is available yet.
So from my point of view the spring solution seems OK (at least for now).
Cheers
Marc
David Bosschaert wrote:
> I think this would be a good improvement since solves the race
> condition that causes the error as raised in DOSGI-66. I'm glad to see
> that some more explanation around the work was provided in the bug as
> well.
> At the moment CXF-DOSGi uses Spring for various things. Its really an
> implementation detail. I think it would be better to refactor that
> dependency into an OSGi Blueprint dependency at some point in the
> future as Blueprint is a standard and Spring isn't. But that's really
> something separate...
>
> Cheers,
>
> David
>
> On 25 February 2010 10:26, Sergey Beryozkin <sb...@progress.com> wrote:
>> Hi
>>
>> My concern is that the way intents maps are loaded is the implementation
>> detail of DSW and even though using Spring is what we use at the moment to
>> load them I'm feeling we should not exclude other options (to make it easier
>> for 'interested' OSGI non-Spring aware containers to integrate/inlcude DOSGI
>> RI). Thus making DSW to start from Spring does not look like an ideal option
>> to me...Also, as I noted in [1], we could find it more difficult to do
>> things other than expressing service registration or dependencies
>> requirements which is what you can do in Spring DM contexts
>>
>> cheers, Sergey
>>
>> ----- Original Message ----- From: "Marc Schaaf" <ma...@marc-schaaf.de>
>> To: <de...@cxf.apache.org>
>> Sent: Thursday, February 25, 2010 9:33 AM
>> Subject: dOSGi: Change the startup of the DSW to Spring
>>
>>
>> Hi,
>>
>> with regard to [1] I would like to change the startup of the dOSGi DSW
>> from a normal OSGi activator to Spring. This way the DSW would be
>> started by the Spring OSGi Extender bundles which would solve an issue
>> with the intent map loading. Currently the intent map is only
>> successfully loaded by the DSW if the Spring OSGi Extender was started
>> before.
>>
>> Are there any objections against this approach ?
>>
>> Thanks,
>> Marc
>>
>>
>> [1] http://issues.apache.org/jira/browse/DOSGI-66
>>
>>
Re: dOSGi: Change the startup of the DSW to Spring
Posted by David Bosschaert <da...@gmail.com>.
I think this would be a good improvement since solves the race
condition that causes the error as raised in DOSGI-66. I'm glad to see
that some more explanation around the work was provided in the bug as
well.
At the moment CXF-DOSGi uses Spring for various things. Its really an
implementation detail. I think it would be better to refactor that
dependency into an OSGi Blueprint dependency at some point in the
future as Blueprint is a standard and Spring isn't. But that's really
something separate...
Cheers,
David
On 25 February 2010 10:26, Sergey Beryozkin <sb...@progress.com> wrote:
> Hi
>
> My concern is that the way intents maps are loaded is the implementation
> detail of DSW and even though using Spring is what we use at the moment to
> load them I'm feeling we should not exclude other options (to make it easier
> for 'interested' OSGI non-Spring aware containers to integrate/inlcude DOSGI
> RI). Thus making DSW to start from Spring does not look like an ideal option
> to me...Also, as I noted in [1], we could find it more difficult to do
> things other than expressing service registration or dependencies
> requirements which is what you can do in Spring DM contexts
>
> cheers, Sergey
>
> ----- Original Message ----- From: "Marc Schaaf" <ma...@marc-schaaf.de>
> To: <de...@cxf.apache.org>
> Sent: Thursday, February 25, 2010 9:33 AM
> Subject: dOSGi: Change the startup of the DSW to Spring
>
>
> Hi,
>
> with regard to [1] I would like to change the startup of the dOSGi DSW
> from a normal OSGi activator to Spring. This way the DSW would be
> started by the Spring OSGi Extender bundles which would solve an issue
> with the intent map loading. Currently the intent map is only
> successfully loaded by the DSW if the Spring OSGi Extender was started
> before.
>
> Are there any objections against this approach ?
>
> Thanks,
> Marc
>
>
> [1] http://issues.apache.org/jira/browse/DOSGI-66
>
>
Re: dOSGi: Change the startup of the DSW to Spring
Posted by Sergey Beryozkin <sb...@progress.com>.
Hi
My concern is that the way intents maps are loaded is the implementation detail of DSW and even though using Spring is what we use
at the moment to load them I'm feeling we should not exclude other options (to make it easier for 'interested' OSGI non-Spring aware
containers to integrate/inlcude DOSGI RI). Thus making DSW to start from Spring does not look like an ideal option to me...Also, as
I noted in [1], we could find it more difficult to do things other than expressing service registration or dependencies requirements
which is what you can do in Spring DM contexts
cheers, Sergey
----- Original Message -----
From: "Marc Schaaf" <ma...@marc-schaaf.de>
To: <de...@cxf.apache.org>
Sent: Thursday, February 25, 2010 9:33 AM
Subject: dOSGi: Change the startup of the DSW to Spring
Hi,
with regard to [1] I would like to change the startup of the dOSGi DSW
from a normal OSGi activator to Spring. This way the DSW would be
started by the Spring OSGi Extender bundles which would solve an issue
with the intent map loading. Currently the intent map is only
successfully loaded by the DSW if the Spring OSGi Extender was started
before.
Are there any objections against this approach ?
Thanks,
Marc
[1] http://issues.apache.org/jira/browse/DOSGI-66