-
Notifications
You must be signed in to change notification settings - Fork 167
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Grid with Custom Components based on PolymerTemplate throw NPE #7116
Comments
Added an scheduler that update grid's data. Interesting that is no errors on 5 seconds period of updates. But on 1 second there is an error occured. Looks like thread unsafe operations. In some cases VaadinService.getCurrent() returns Null. |
grid_update.zip
The error occured on my machine with these parameters when starts app. When error occured - the Thread ID with absent VaadinService is printed to console. Testing environment: |
The reason of NPE is apparently But stacktrace shows that the code is invoked inside |
As a workaround for this bug you may use protected constructor |
So
|
Vaadin 14.1.1
I create own class component that extends PolymerTemplate.
Then i construct simple View extends VerticalLayout:
Then i take NPE on view access from browser.
I look at default constructor of PolymerTemplate:
The
VaadinService.getCurrent()
return NULL.It looks like similar to #3789. From it i saw that i need to create components in current UI context. Is it true? If yes, why it is necessary? And why there is invocation of
isCompatibilityMode()
? Is this redundant in the current version of Vaadin?The text was updated successfully, but these errors were encountered: