Support multiple independent roots

[RichoDemus]

I want to be able to deploy multiple roots in different paths, like this:

http://localhost/api/v1/ -> resources/api/v1/queyr.graphqls
http://localhost/api/v2/ -> resources/api/v2/queyr.graphqls

and then also have different query resolvers as well.

If this is already possible then if someone can tell me how I can open a PR to update the documentation

[oliemansm]

@RichoDemus Currently it just exposes one GraphQL Servlet on one endpoint. To be able to do this would require some work, and you might run into a couple of challenges while doing so.

You need to create a GraphQLSchema per path, which by the autoconfiguration is done for one path by creating a SchemaParser like this:

    @Bean
    @ConditionalOnBean({GraphQLResolver.class})
    @ConditionalOnMissingBean
    public SchemaParser schemaParser(
            List<GraphQLResolver<?>> resolvers,
            SchemaStringProvider schemaStringProvider,
            PerFieldObjectMapperProvider perFieldObjectMapperProvider
    )

See

graphql-spring-boot/graphql-spring-boot-autoconfigure/src/main/java/com/oembedler/moon/graphql/boot/GraphQLJavaToolsAutoConfiguration.java

Line 60 in 0da8ab6

public SchemaParser schemaParser(

.

You probably could use the same approach, having a similar method where at least all resolvers are automatically injected. Then using a custom SchemaStringProvider per path you can create a SchemaParser per path which you can convert into GraphQLSchema by calling schemaParser.makeExecutableSchema().

Then you can use those GraphQLSchema instances to register two servlets. First you create a servlet out of the schema by calling GraphQLHttpServlet.with(graphqlSchema). Which you can then wrap into a servlet for Spring:

    @Bean
    public ServletRegistrationBean<AbstractGraphQLHttpServlet> api1(AbstractGraphQLHttpServlet servlet) {
        return new ServletRegistrationBean<>(servlet, "/api/v1");
    }

    @Bean
    public ServletRegistrationBean<AbstractGraphQLHttpServlet> api2(AbstractGraphQLHttpServlet servlet) {
        return new ServletRegistrationBean<>(servlet, "/api/v2");
    }

See https://github.com/graphql-java-kickstart/graphql-spring-boot/blob/master/graphql-spring-boot-autoconfigure/src/main/java/com/oembedler/moon/graphql/boot/GraphQLWebAutoConfiguration.java.

One way would be to start by configuring graphql-spring-boot in a way to configure one of the paths for you using one of the SDLs and then add a @Configuration class to your project to create the other one. Hope this helps.

[oliemansm]

Closing this issue due to inactivity.

[ieugen]

One approach that I believe is suitable in this case is to package the apps as WAR's and deploy them separately. If you build the war's in the same project they can share the modules and most of the code and benefit form isolated deployment since WAR's are 'standalone' apps.

[ieugen]

@oliemansm : We reached this issue/thread again and it's a functionality that I think it is useful.
Are you willing to accept a patch for this? If we go this route we would lie to have it supported upstream. I'm willing to do the work needed to get upstream but I would like to have a Yes we are interested or No, don't bother.

Also, what are your conditions / requirements for the patch so I can take them into consideration.
IMO, this is important when dealing with breaking changes that might occur.

[gchiappe]

+1 for this functionality. It would be very useful for different escenarios including api versioning. Configuration should be simple, like @RichoDemus example. I think the schemas folder and servlet mappings can be set in the application properties file.

[PhilippS93]

Would be really helpful to have this feature on board.

[oliemansm]

Reopening the issue seeing the popularity of the request. @ieugen Thanks for offering to help out here. We're very short handed so any support is appreciated. The basic principles mentioned by @gchiappe seem like a good starting point.

The WARs approach doesn't immediately come to mind to me since that implies certain consequences regarding deployment, making it potentially incompatible (unless I'm totally misunderstanding your proposed solution here).

[ieugen]

Hi @oliemansm , I'm not currently working on with GraphQL or this library so I won't be available to help.
If things change I will let you know.

The WAR approach is to build 2 apps that share jar files (code).
They are basically independent and not a first option on the solutions list.

[klabast]

Hi, are there any plans to implement this? It would be quite a useful feature. @oliemansm your suggestions seems reasonable, but I still wouldn't know how to approach this effectively...

[olahellgren]

Just a comment to this if you need two endpoints with the same schema, it's possible to add additional url mappings to one servlet.

@Bean
public ServletRegistrationBean<AbstractGraphQLHttpServlet> graphQlServletRegistration(AbstractGraphQLHttpServlet servlet) {
  var servletBean = new ServletRegistrationBean<AbstractGraphQLHttpServlet>(servlet, servletGraphQlMapping);
  servletBean.addUrlMappings(nonAuthorizedGraphqlPath);
  return servletBean;
}

[domenpetric]

Is there any way to expose 2 endpoints in the latest version?

[Jojoooo1]

any news ?