Hi Andrew!
Just tried out the latest version of equinox aspects and am
successfully weaving against OSGi head. That's great.
:-)
However, I am still getting an error when the equinox aspects weaver
is started at level 1. This problem goes away if I start it instead
at level 4.
Hm, that
Hi All,
I currently prototype a little Equinox app that uses Declarative Services (DS).
The DS spec 4.1 says The service element is optional. ... The service element
must have one or more provide elements that define the service interfaces. So,
the following XML is syntactically correct and
Looks like a bug to me. Open a bug here:
https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Equinox
Select the Compendium component and start the summary with [ds].
The schema for the XML only permits a single service element. DS should
reject the XML as invalid thus ignoring the component
Bug 252355 https://bugs.eclipse.org/bugs/show_bug.cgi?id=252355 filed.
Kai
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of BJ Hargrave
Sent: Dienstag, 28. Oktober 2008 14:28
To: Equinox development mailing list
Subject: Re: [equinox-dev] service elements in Declaratice
Hi Kai,
I think that this is a bug. According to XML schema that defines the
component description grammar there is:
element name=service type=scr:Tservice minOccurs=0 maxOccurs=1/
So only one occurrence is allowed.
---
Regards/Pozdrowienia,
Lukasz Bobowiec
Software Engineer
Tivoli Dynamic
As I mentioned earlier in this thread, I think it has something to do
with the simple configurator bundle
(org.eclipse.equinox.simpleconfigurator_1.0.0.v20080604.jar) and how
it is used to bootstrap the loading of other bundles.
Here is the exception I get (the first line of the stack trace
Hi Andrew,
this sounds quite reasonable. Can you try to set the start level of the
simpleconfigurator to 1 and of the weaving service to 2 to see what happens?
-Martin
Andrew Eisenberg wrote:
As I mentioned earlier in this thread, I think it has something to do
with the simple configurator
