graphql-spring-boot-starter | Spring boot starter for GraphQL | GraphQL library

So I'm new into GraphQL and i got stuff running by manually setup a schemaparser and datafetchers. But I want to refactor and try out by implementing GraphQLQueryResolver to a class and controll my queries from there.

I get it to work by making a new project, but with the same dependencies and should be same implementation, It doesn't run. When I delete the query-methods which reflects the schema, I'll get the error that I need to add methods based on the Queries in the schema, so I get the confirmation it reaches the class-file with the implementation of the GraphQLQueryResolver. But I still get this error when i add the rights methods:

I am building a graphql application with spring-boot-starter-webflux 2.5.6 and com.graphql-java-kickstart:graphql-spring-boot-starter:12.0.0. At this point the application is running fine since com.graphql-java-kickstart is easy to start with. With http-Requests I can call Queries and run Mutations and I am even able to create and get updates via Subscriptions over websockets.

But for my application Queries and Mutations also have to run via websocket.

It seems that in com.graphql-java-kickstart:graphql-spring-boot-starter you can only configure a subscription endpoint as websocket. Adding an additional websocket via 'extends Endpoint' and '@ServerEndpoint' did nothing at all.

I also tried to add my own HandlerMapping:

I just setup a new Spring Boot application with GraphQL Java Tools. The precise versions in my Maven pom.xml file are:

• com.graphql-java-kickstart:graphql-spring-boot-starter:12.0.0
• com.graphql-java-kickstart:graphiql-spring-boot-starter:11.1.0
• com.graphql-java-kickstart:graphql-java-tools:12.0.0

Although my application compiles, when I start my Spring Boot application, it fails with the following cryptic error:

I'm "up the middle" Spring Boot 2.5.4 with graphql-java-16.2 brought in via some org.springframework.experimental/graphql-spring-boot-starter dependency. The GraphQL Java Documentation suggests that I can just BigDecimal something up in my Schema: https://www.graphql-java.com/documentation/v16/scalars/

I have a library project that I use to hold some setup for my other projects that has a lot of utility classed and also utility libraries included. So, I changed all my "implementation" calls in the library's build.gradle to "api" calls so I don't need to reimport the dependencies again and again. After building the library and moving the jar from my library folder to the lib folder inside my main project, I can access all the classes in my library, but the transitive dependencies are not available in my main project.

I also tried using implementation and transitive = true, but no luck.

I'm using AdoptOpenJDK 16 and Gradle 7.0 and I already tried to rebuild everything after cleaning the cache.

library's build.gradle

I'm attempting to take advantage of Spring Cloud Kubernetes in my Spring Boot-based microservice, namely autoconfiguration and service discovery.

However, I get an error message (Timeout waiting for informers cache to be ready, is the kubernetes service up?) during the initialization, as well as high verbosity, both of which I am unable to find information online to help me pinpoint the cause. Error message and excessive log messages are detailed below. Apologies for the lack of context, but I'm also puzzled!

The application is running within the default service account, which has all the permissions specified in the documentation:

I'm trying to use two libraries together, GraphQL and Jmix.

I created the Jmix project using Intellij's new project wizard (with the Jmix plugin installed) then I added GraphQL to Gradle using the standard graphql-spring-boot-starter. Then I wrote a schema and the resolver beans.

But during startup, an exception is thrown because the WebSocket endpoint /subscriptions is being registered twice on Tomcat. (I tried changing the endpoint by using the application property graphql.servlet.subscriptions.websocket.path, but that is not the issue.)

After some digging, I found that the classes GraphQLWebsocketAutoConfiguration from graphql-spring-boot-autoconfigure and VaadinAutoConfiguration from jmix-ui-starter are both registering a ServerEndpointExporter bean, which is not supposed to happen.

Here is graphql's code:

I am implementing basic GraphQL application in Spring Boot by using following library.

My question is: what is the best when implementing resolving methods? direct call of data repositories or calling back a main resolver aka one implementing GraphQLQueryResolver (provided it has appropriate methods)? in other words (see example below), is the DataFetchingEnvironment properly adjusted/set when calling back a main resolver?

Note: if you're not familiar with how Resolvers work with GraphQL Java Tools, I'll just let you have a look @ https://www.graphql-java-kickstart.com/tools/schema-definition/

Now the example.

In a Spring Boot app, with GraphQL Java Tools (with the graphql-spring-boot-starter dependency), let's have this schema: