-
Notifications
You must be signed in to change notification settings - Fork 40
Closed
Labels
questionFurther information is requestedFurther information is requested
Description
Hi,
I was trying to implement the graphql-kickstart-spring-boot-starter-webflux and kept running into the below error. I tried cloning the sample spring-boot-webflux repo, but ran into the same issue as well.
Parameter 1 of method webSocketHandlerMapping in graphql.kickstart.spring.webflux.boot.GraphQLSpringWebfluxAutoConfiguration required a bean of type 'graphql.kickstart.spring.webflux.ReactiveWebSocketSubscriptionsHandler' that could not be found.
Action:
Consider defining a bean of type 'graphql.kickstart.spring.webflux.ReactiveWebSocketSubscriptionsHandler' in your configuration.
When I then try to implement a bean of ReactiveWebSocketSubscriptionsHandler, it resolves the startup error but doesn't start
@Bean
public ReactiveWebSocketSubscriptionsHandler reactiveWebSocketSubscriptionsHandler(ReactiveSubscriptionsProtocolFactory subscriptionProtocolFactory) {
return new ReactiveWebSocketSubscriptionsHandler(subscriptionProtocolFactory);
}
But it doesn't start up the /graphql or /subscription endpoints.
2020-05-24 21:41:42.289 INFO 23511 --- [ main] webflux.WebfluxApplication : No active profile set, falling back to default profiles: default
2020-05-24 21:41:43.596 INFO 23511 --- [ main] o.s.b.web.embedded.netty.NettyWebServer : Netty started on port(s): 8080
2020-05-24 21:41:43.606 INFO 23511 --- [ main] webflux.WebfluxApplication : Started WebfluxApplication in 1.493 seconds (JVM running for 2.156)
Am I missing something else that isn't documented?
Metadata
Metadata
Assignees
Labels
questionFurther information is requestedFurther information is requested