Hi,
I've been making runs through Eclipse-generated Equinox frameworks, and
eventually pulled in the Stanbol bundles I needed.
From an OSGi console ss I can see bundles are activated, but their
components are not. I don't see the effects of any execution of the
activate() methods at least.
So the bad news is that SCR components seem to be ignored. The good news
is that this doesn't seem to prevent bundles from activating. Looks like
this means having a fallback strategy for non-Felix environments.
Alessandro
On 12/15/10 4:06 PM, Bertrand Delacretaz wrote:
Hi,
On Wed, Dec 15, 2010 at 3:54 PM, Alessandro Adamou<[email protected]> wrote:
...I'd like to test Stanbol bundles on an OSGi environments other than Felix,
esp. Equinox.
Before setting up the environment, I was wondering if I can expect these
bundles to run despite the fact there are Felix SCR components and services....
In theory yes, I'm not sure about our Sling-based launcher but you
might not even use it IIUC.
In my understanding, declarative services are part of the OSGi
specifications, but what if in the Java code they are defined with Felix
annotations (@Component, @Reference etc.)? Are they converted to
"standardized" component/service declarations at build time? I haven't found
anything of much use in the generated MANIFEST.MF files...
The annotations are processed at build time by the maven-scr-plugin
[1] so they have no impact at runtime.
The result is written to serviceComponents.xml files found at
target/classes/OSGI-INF/serviceComponents.xml for modules that call
this maven plugin. Those xml files get included in the bundles and
that's what the SCR subsystem uses.
-Bertrand
[1] http://felix.apache.org/site/apache-felix-maven-scr-plugin.html
