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
ich is what you can do in Spring DM contexts
cheers, Sergey
- Original Message - From: "Marc Schaaf"
To:
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
Hi David,
I'm sorry but I currently don't have the time to implement the test
cases. I will add them as soon as possible, probably in two weeks from
now when I will have some more time on my hands.
Cheers,
Marc
David Bosschaert wrote:
> Thanks Marc!
> One comment I have is that there are no CX
ndardizes the interfaces between internal components
> Remote Services implementations typically have. A Distribution
> Provider, Topology Manager and Discovery System. This makes it
> possible to mix&match these components from various implementations.
> For more information see slides 6
rk (and update the docs) - this is
>> something I would be happy to help out with.
>> * When the above is done, cut the actual release candidate(s).
>>
>> Cheers,
>>
>> David
>>
>> On 11 June 2010 15:32, Marc Schaaf wrote:
>>
>>> Hi,
&
+1
Cheers,
Marc
Am 21.07.2010 08:45, schrieb Eoghan Glynn:
Folks,
Now that the release notes are all fixed up, I'm calling a second vote to
release
CXF Distributed OSGi 1.2.
The release notes contain a description of new features and bugs fixed
in this release:
http://svn.apache.org/repos/
