Vaadin resources publish issue in OSGI environment
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.8k
- Forks
- 717
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 3
Description
When vaadin resources bundles (e.g. vaadin-server, vaadin-themes, vaadin-client-compiled) starts before vaadin-shared, an exception "Vaadin Shared is not active!" is raised, and resources will not been published until bundles restart.
Maybe its would be better to publish vaadin resources (resources in VAADIN folder, like bootstrap.js) as well as themes and widgetsets (through OSGI services).
Vaadin Framework version: 8.2.0
OSGI Environment: Apache Karaf 4.1.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the startup-order failure with Vaadin Framework 8.2.0 in Apache Karaf 4.1.4, with vaadin-server, vaadin-themes, and vaadin-client-compiled starting before vaadin-shared. Trace the resource publication path and the "Vaadin Shared is not active!" exception; done means resources, themes, and widgetsets publish without requiring bundle restarts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100