Hi Thomas,
What do you think about forking flow and playing around with it from a modern
OSGi perspective.
Might be a case of the blind leading the blind.
If we do not get anywhere or they solve the problems earlier or it takes up too much time, we just
abandon it.
They do not really want to do the OSGi version, they are happier with Spring, same as most java
devlopers :-(
Paul
On 5/02/2019 7:49 pm, Thomas Driessen via osgi-dev wrote:
Hi,
this is just an information for those of you who are interested in using Vaadin
and OSGi together.
Although Vaadin is making V10+ OSGi compatible (adding manifests, using BundleTracker instead of
ServletContainerInitializer, etc.) they do not yet have integrated Declarative Services as they
did for V8-. The former integration of V8- enabled a developer to declare a Vaadin UI to be a
component in OSGi, thus being able to reference other services. This is not yet possible in V10+
where UIs are replaced by @Route annotated classes.
I'm trying to add such an integration and if anyone on this mailinglist is interested in such a
support (I think at least Paul will be ;) ) then don't hesitate to comment/vote up the respective
issue at Vaadin (https://github.com/vaadin/flow/issues/5017) or comment/contribute on/to the
implementation sketch (not working yet) at Github (https://github.com/Sandared/flow-osgi)
As I'm fiddling around with (at least for me) advanced DS stuff, please let me know if I do not
adhere to some known best practises/am messing up the implementation/did an awfully bad design or
anything else (You live and learn ;) ).
Kind regards,
Thomas
_______________________________________________
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
