Jan Martiska

> I have another problem with this approach: If I have a Java SE client, e.g. in a test, the Jandex has not been scanned. I would love to use...

Hm WildFly still compiles with Java 11 and supports applications running on it, so by switching something to 17 we would break it :( Also regarding the sealed interfaces: Do...

The whole SmallRye org uses one common strategy and build+release system that runs with JDK 11 (and it will stay like this until WildFly moves to 17+), I don't see...

> IIUC, the model-builder is only used in Quarkus, and it has a dependency on Jandex, so we can't use it, can we? Currently, it is only in Quarkus, but...

Ah ok, thanks for the clarification. Yeah if the OS kills the connection after some time, that's good. We could implement some custom timeouting, but we will also need to...

You can already accomplish the same by doing ``` @Mutation public String add(UserOrComment userOrComment) { ... } @OneOf class UserOrComment { // user, comment fields + getters and setters }...

> The `@oneOf` is currently only a directive defined on the server side. I'm not sure there is already any validation. > There is validation for it built into graphql-java

We bring in Yasson anyway so I guess using its classes wasn't considered a problem, but if we can remove that, then why not. I'm not sure how often that...

I have to say that using the `-parameters` argument generally is considered required for Quarkus applications. If you don't have it, there's a lot of other ways that your app...

This was fixed in SmallRye GraphQL 2.1.0, so that will be in Quarkus 3.0. With a build of the current Quarkus `main` branch, the response with the error is this:...