Martin Kouba

> My understanding is that EJB also has to implement the full Interceptors specification, just like CDI, so even though the idiomatic way of associating interceptor with components in CDI...

> @mkouba I also wonder if we should add a note/tip/whatever at the top of https://quarkus.io/guides/websockets to point people to WebSockets.next as our preferred way to use WebSockets nowadays? >...

So if you look at [the docs](https://quarkus.io/guides/qute-reference#global_variables), you can read that _Global variables are added as computed data of any TemplateInstance during initialization_. In other words, for each global variable...

I don't think it's inconsistent. It may not seem intuitive but if you look at the template hierarchy there's the [top-level template](https://github.com/gbourant/global-qute/blob/master/src/main/java/gr/HelloResource.java#L31) which calls a user tag by means of...

> In Qute case were are (in the current state) dealing with ids. Yes, in Qute we use template ids which are _absolute/full paths_ for file-based templates located in `src/main/resources/templates`....

> we could also have the same system you added on templates with priorities Yes, we could apply the same defaults, i.e. root archive message files take precedence. The logic...

So one of the solutions would be to: 1. support duplicit message files with different priorities 2. application root will be the highest priority, e.g. `10` 3. other application archives...

@gbourant The `io.quarkus.qute.ResultMapper` is the API that should be used for this kind of stuff. However, it's applied globally. Result mappers are sorted by priority (higher goes first) and there's...

So my understanding of the new `ServerWebSocketImpl#tryHandshake()` impl is that it attempts to read the `volatile` field first and if not `null` then no `synchronized` block is needed. This is...

> > Set --allow-incomplete-classpath by default in when Quarkus runs a native compilation > > You essentially need to avoid passing `--link-at-build-time`, which can be achieved through the `NativeImageAllowIncompleteClasspathBuildItem`. Hm,...