marcin
marcin
Starter app should be updated after merging https://github.com/vaadin/flow/pull/14303
> Currently I face the issue that I can't use Spring Boot 2.7.0+ with the latest VAADIN version (23.1.3). When using Spring Boot 2.7.0+, the page reloads automatically every now...
I've updated that reflection method during work on jakarta ee 9 (servlet 5) https://github.com/vaadin/flow/commit/c2430cc7fc8c492e51daef85416b7cc68a44da11 - CP to master? I've tested on 17.0.3 with Wildfly 26.1.1.Final (preview)
> This also fixes first WARN mentioned in #13868 The `pattern='/images/*.png'` is in the starter application so should be fixed there after this is merged. Also stareters should be updated...
> Same thought about the old `configure(WebSecurity web)` Should we maybe expose a `WebSecurityCustomizer` bean with logic previously from `configure(WebSecurity web)`? If we adopt the same pattern, the migration would...
Tested on MacOS 12.4 on Safari Version 15.5 (17613.2.7.1.8) and Chrome Version 103.0.5060.114 (Official Build) (arm64) and on both it looks the same - no push reopening:
> Is `VaadinServletContext` a singleton? Otherwise locking will have no effect @Artur- indeed, so why to lock on VaadinContext in FeatureFlags if they call setAttributes which already locks on ServletContext?
Can be closed as fix is available in https://github.com/vaadin/flow/pull/14638
Developed under https://github.com/vaadin/osgi/tree/feature/jakarta-servlet5 Latest version of Felix 7 is not compatible with Jetty 11. There is [ongoing work on Felix 8](https://github.com/apache/felix-dev) that supports Jetty 11. I have been trying to...
@Legioth @Artur- @TatuLund - do we have any conclusions? Is I understand from above: > introduce API to configure it work differently when needed Implementing configuration property to disable offlinePage...