Migrating to spring-grapql from graphql-java-kickstart

[MohamedAymanN]

We are migrating to spring-graphql from graphql-java-kickstart. But we wanted to do it incrementally, given we have a lot of resolvers. Thus, we wanted to have both dependencies living by side and move each resolver slowly. Is it possible to achieve this, or are there a lot of conflicts?

For instance I tried it and got:
Unresolved failure from "ASYNC" dispatch: java.lang.ClassCastException: class graphql.GraphQLContext cannot be cast to class com.klarna.app.cons.graphql.ExtendedGraphQlContext (graphql.GraphQLContext and com.klarna.app.cons.graphql.ExtendedGraphQlContext are in unnamed module of loader 'app')

Appreciate your help

[bclozel]

It's not clear from your description what is the issue. Could this be a graphql-java version incompatibility between Spring for GraphQL and graphql-java-kickstart? A complete stacktrace would also help, as it's not clear whether this comes from Spring for GraphQL or graphql-java-kickstart.

In general, we don't guarantee that spring-graphql can run side by side with graphql-java-kickstart but we can have a look if you have a minimal sample application that demonstrates the problem.

[rstoyanchev]

It sounds like you have a custom GraphQL context object, but Spring for GraphQL relies on the default GraphQLContext that is configured by default. You can try setting one through the ExecutionInput from an interceptor.

[MohamedAymanN]

Unfortunately, I do not see anything else in the stack trace except the above error. I also tried added an intercepter as per your suggestion but I still receive the same error.

[MohamedAymanN]

I am not sure at which point during handling the response, would it try convert the GraphQLContext to the Custom context we have for the kickstart, as it implements an interface GraphQLKickstartContext

[vyj7]

We migrated from kickstart from Spring graphql. It was smooth. It became easy because we didn't have to rewrite batchloaders and dataloaders as it supports which we did for kickstart.
Only changes are removing context with interceptor so that we can have customContext and then syntax changes for query mutation.

[rstoyanchev]

@MohamedAymanN it sounds like you depend no a specific type of GraphQLContext. This is very much possible by setting it on the ExecutionInput through an interceptor. Please, review the link to the documentation I provided above. And more generally, as you are switching, I suggest reviewing the documentation more broadly in order to become familiar and understand any differences with what you may be used to.

I am closing this issue as there isn't anything further we need to do.