Marco Collovati

> This doesn't really make sense to me, because it breaks context-mapping portability of Vaadin I don't see any problem with context mapping, since every deployed webapp is isolated, and...

@archiecobbs Thanks for clarifying

> Aside from any principles, it's obviously the case that the "If not, the servlet container takes care of static resource requests" part is not correct, because otherwise we wouldn't...

Would a `RewriteRule` with `[P,L]` flags and a `RewriteCond` help to proxy websocket upgrade requests via `ws://....`?

Since Vaadin 23 class scanning order is predictable in development mode: classes to inspect are sorted by name (`Class.getName()`) and `@NpmPackage` annotations are processed top-down according to the class hierarchy,...

Interesting benchmarks. At a first look it seems that, apart from performance, Kryo seems easier to customize, has better documentation and also some OOB serializer implementation in a side project...

> There are many use cases for custom Serialization, but once a serialiser (eg, Kryo) is employed, I cannot think of a reason to drop back into native Java serialisation....

Probably related to this [issue](https://github.com/vaadin/flow/issues/18869), that has been fixed in Flow and will be released in Vaadin 24.3.7

I agree with Knoobie. The navigation is still ongoing during view creation. Furthermore, the current view itself could not be in the location chain, since it is currently in creation....

@mvysny I think the information is currently only available in the event itself during view construction. A potential workaround could be to have a custom `Instantiator` that overrides `createRouteTarget(Class routeTargetType,...