Hi Paul, The error you’re seeing is a resolution failure because the "com.vaadin.flow.osgi version=1.2.3” bundle has a requirement in the “osgi.service” namespace for the service with interface “org.osgi.service.http.HttpService”. This basically says that the Vaadin flow bundle is trying to use the HttpService in some way, and therefore the exported application needs to include a bundle which provides the HttpService.
Now in fact the Felix Http Jetty implementation used in OSGi enRoute *does* provide this service, however it is missing the metadata from the manifest saying that it provides this service. This is a packaging bug in the Felix Jetty bundle, and is why the resolve fails. There is a further question, which is why on earth the Vaadin Flow bundle is using the HttpService? It would be better and easier for them to use the Http Whiteboard than to use the old HttpService to provide content… Best Regards, Tim > On 16 Jan 2019, at 04:45, Paul F Fraser via osgi-dev <osgi-dev@mail.osgi.org> > wrote: > > Hi, > > Following the process below I have sucessfully managed to run a vaadin flow > bundle in OSGi. > > Create vaadin flow bundle in enroute maven project. > https://github.com/QNENet/enRouteQNEFlow-0.0.1 > <https://github.com/QNENet/enRouteQNEFlow-0.0.1> > Use flow bundle in bnd workspace and export as jar, which of course contains > all necessary dependencies. > java -jar flow.jar works at localhost:8080 > https://s3-ap-southeast-2.amazonaws.com/qnenet/vaadinFlow/flow.jar > <https://s3-ap-southeast-2.amazonaws.com/qnenet/vaadinFlow/flow.jar> > create application from enRoute archetype > Add all dependencies as used in exported bnd workspace flow.jar > enRoute app fails. > [ERROR] Failed to execute goal > biz.aQute.bnd:bnd-export-maven-plugin:4.1.0:export (default) on project > flow-app: Unable to resolve <<INITIAL>>: missing requirement > osgi.identity;filter:='(osgi.identity=com.vaadin.flow.osgi) > <filter:='(osgi.identity=com.vaadin.flow.osgi)>' [caused by: Unable to > resolve com.vaadin.flow.osgi version=1.2.3: missing requirement > osgi.service;filter:='(objectClass=org.osgi.service.http.HttpService)';effective:='active > > <filter:='(objectClass=org.osgi.service.http.HttpService)';effective:='active>'] > -> [Help 1] > > Any assistance to solve this last (?) hurdle to having an OSGi work > environment for vaadin flow development would be most appreciated. > > Thanks > > Paul Fraser > > > > > > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
