Vaadin resources publish issue in OSGI environment

[arotnov]

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

[arotnov]

By the way, its very strange to see OsgiVaadinResources class in its current implementation for OSGI purposes, while all publish works are doing by VaadinResourceService and VaadinResourceTrackerComponent (whiteboard pattern).

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[elmot]

Still valid

[ZheSun88]

hi, recently, we have quite a few changes on this related issue. Could you test your project with the new released framework version 8.6.0.alpha2? Thanks.

[arotnov]

hi, recently, we have quite a few changes on this related issue. Could you test your project with the new released framework version 8.6.0.alpha2? Thanks.

Yes. I will test it during this week.

[arotnov]

I perform tests with Apache Karaf 4.2.1 and Pax Web 7.2.3: Then vaadin-shared bundle starts earlier than other resource contribution bundles (vaadin-server, themes, push) - no resources are published by http service. Then vaadin-shared starts after resouce contribution bundles, resources are published. Custom themes and widgetsets (contributed by OsgiVaadinTheme and OsgiVaadinWidgetset services) are also not published after starting of vaadin-shared (after activation of VaadinOsgiTrackerComponent). I think a problem is in resource registration logic in VaadinOsgiTrackerComponent - resources are actually registered only in activate() method, called once - when HttpService is binded to component.

[ZheSun88]

still valid.

[Maurice-Betzel]

I do a programmatic restart of the Vaadin shared bundle if i detect undeployed servlets in my Karaf container as a workaround.

[TatuLund]

Is this problem still with 8.6.3?

[arotnov]

With 8.6.3 resources registraction (by OsgiVaadinContributor) works normal with any startup level. Ploblem is still valid for VaadinServlet whiteboard registraction (provided by osgi-integration bundle).

[stale[bot]]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!

[TatuLund]

Has this been retested with Vaadin 8.9?

[stale[bot]]

Hello there!

We are sorry that this issue hasn't progressed lately. We are prioritizing issues by severity and the number of customers we expect are experiencing this and haven't gotten around to fix this issue yet.

There are a couple of things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are dozens of duplicates in our issue tracker, so it is possible that the issue is already tackled. If it appears to be fixed, close the issue, otherwise report to the issue that it is still valid.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• Try fixing the issue yourself and create a pull request that contains the test case and/or a fix for it. Handling the pull requests is the top priority for the core team.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!