The scr:list output shows they are published by two separate bundle IDs,
112 and 137. Check whether you have accidentally built the component class
into both bundles.
Neil
On 18 Jan 2018 11:45 pm, "Erwin Hogeweg via osgi-dev" <
osgi-dev@mail.osgi.org> wrote:
Hi,
I have a very simple component,
Thanks Bernd,
The service descriptor is created off of the @Component annotation and seems
ok. Nothing out of the ordinary in the manifest either as far as I can see.
http://www.osgi.org/xmlns/scr/v1.3.0;
name="my.service" configuration-policy="require" activate="activate"
I would start with inspecting the produced bundle (Jar), especially the
manifest and the service descriptors. Maybe you have two conflicting maven
plugins?
Gruss
Bernd
--
http://bernd.eckenfels.net
From: osgi-dev-boun...@mail.osgi.org
Hi,
I have a very simple component, with only one method, which is referenced in
only one other component. For some reason though, the OSGi framework decides
that the component needs to be instantiated and registered twice. I have put
breakpoints in the constructor and in both cases the entire
Hi Paul,
right now I'm using a mixture of Vaadin 8.2.1 bundles, the enroute code
and a little bit of current vaadin bugfixing code ;)
If you start all vaadin bundles (com.vaadin.shared, com.vaadin.server,
com.vaadin.external.gentyref, com.vaadin.client-compiled and
com.vaadin.themes) vaadin
On 19/01/2018 2:15 AM, Thomas Driessen wrote:
Hello,
just for other people that are trying to get Vaadin 8 to work within an OSGi
environment:
Hi Thomas,
Good to hear that you are on the way.
Are you now using all Vaadin OSGi bundles and none of the enRoute bundles?
Are you developing in
Hello,
just for other people that are trying to get Vaadin 8 to work within an
OSGi environment:
The ClassNotFoundException for AppWidgetset can be ignored. If Vaadin
does not find this class it falls back to the default widgetset.
The lost connection seems to stem from false urlPatterns
