Hi,
Past OSGi examples for Vaadin used a staticResources bundle which looked through all bundles to find
Vaadin resources.
Using EnRoute should I investigate (ask for help!) developing an extension annotation to perform
this task or should I stick with the staticResources approach?
It seems to me that the EnRoute handling of statics and resources fits nicely with the requirements
for Vaadin.
To use Vaadin with OSGi in the past I have found a usable workflow to be
1. Create normal Vaadin project.
2. Create war in Vaadin project.
3. Extract VAADIN resources etc. from war into OSGi project as necessary.
Vaadin now provides ability to create Spring Boot projects but have not worked
on OSGi.
Paul Fraser
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
