Fix links to Boot "Web Endpoints" section and mention WebSocket endpoint not enabled by default

[dsarlo-viso]

I'm currently trying to set up a basic graphql project using Spring-Graphql. When starting the project, I first set it up using the com.graphql-java-kickstart graphql-spring-boot-starter and spring boots websocket starter and had everything working. When attempting to listen on ws://localhost:8080/subscriptions it would connect and start listening and would pull data. I then found this project and wanted to switch. I changed everything over, my queries work great, but now, when I try to connect to ws://localhost:8080/subscriptions to listen for subscriptions, I get the following error in the graphql playground.

{
  "error": "Could not connect to websocket endpoint ws://localhost:8080/subscriptions. Please check if the endpoint url is correct."
}

Seems as though the websocket component is not being stood up by the starter provided.

Note: I have the following property set in my config - spring.graphql.websocket.path=/subscriptions

[rstoyanchev]

Try debug/trace logging on both sides and examine the output. If you want us to help you'll need to provide more detail, an isolated sample preferably.

[dsarlo-viso]

@rstoyanchev When adding a subscription, the graphql-spring-boot-starter from com.graphql-java-kickstart automatically stands up the websocket on localhost:8080/subscriptions.

With this project, the spring.graphql.websocket.path application property must be set. When looking at the documentation, I was able figure that out, but it isn't referenced clearly (you have to search a tiny bit).

The following doc contains a url to the "Web Endpoints" section of spring boot documentation, but it looks like the header has since been changed.

Perhaps that can be relinked to this instead web.graphql.transports.http-websocket

TLDR;
The spring.graphql.websocket.path application property must be set and I had a caching issue locally with some gradle dependencies which is why the above property seemingly wasn't working for me. All good now.

[rstoyanchev]

Okay thanks for the tip on the outdated documentation link, we'll take care of that!