[MGNLUI-5683] Fail gracefully when facing a faulty component binding Created: 25/Feb/20  Updated: 06/Mar/20  Resolved: 06/Mar/20

Status: Closed
Project: Magnolia UI
Component/s: None
Affects Version/s: 6.2
Fix Version/s: 6.2

Type: Improvement Priority: Major
Reporter: Mikaël Geljić Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: UI Framework 18
Story Points: 1

 Description   

e.g. trying to map components to obsolete/renamed interfaces prevents the whole Admincentral's VaadinServlet from starting properly. Even misleads to believe there's an issue with the widgetset.

[http-nio-8080-exec-7] com.vaadin.server.VaadinServlet.serveStaticResourcesInVAADIN Requested resource [/VAADIN/widgetsets/com.vaadin.DefaultWidgetSet/com.vaadin.DefaultWidgetSet.nocache.js] not found from filesystem or through class loader. Add widgetset and/or theme JAR to your classpath or add files to WebContent/VAADIN folder.

(not sure why Vaadin would try to load a "default UI" with DefaultWidgetSet, anyway)


Generated at Mon Feb 12 09:29:00 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.