eb9b1f308d
Prior to this commit, GraphQL applications using the WebSocket transport would fail with an `java.lang.IllegalArgumentException: No JSON Encoder` as the JSON codec was reflecting on the `GraphQlWebSocketMessage` to check that it can handle this type, during startup time. `GraphQlWebSocketMessage` is the message type being used for sending and receiving GraphQL requests. This commit registers binding reflection on this type as soon as a `GraphQlWebSocketHandler` (mvc or webflux) is registered as a bean in the application. This type is also used on the client side in the client `WebSocketGraphQlTransport`. Because clients cannot be reliably detected here in the application context or via classpath checks, this commit also adds a JSON metadata file that adds reflection on the type, if and only if the `WebSocketGraphQlTransport` is reachable by the static analysis performed by GraalVM. Fixes gh-560
Spring for GraphQL 
GraphQL support for Spring applications with GraphQL Java.
Code of Conduct
This project is governed by the Spring Code of Conduct. By participating, you are expected to uphold this code of conduct. Please report unacceptable behavior to spring-code-of-conduct@pivotal.io.
Documentation
This project has reference documentation (published and source), an API reference. The are samples in the 1.0.x branch that will be moved out into a separate repository.
Continuous Integration Builds
Information regarding CI builds can be found in the project's Concourse pipeline documentation.
Stay in Touch
Follow @SpringCentral.
License
This project is released under version 2.0 of the Apache License.