[
https://issues.apache.org/jira/browse/SLING-9800?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17224695#comment-17224695
]
Bertrand Delacretaz commented on SLING-9800:
--------------------------------------------
bq. ...the resource of the request is the Servlet ...
Not sure what this means but what happens under the hood in the
[DefaultSchemaProvider|https://github.com/apache/sling-org-apache-sling-graphql-core/blob/master/src/main/java/org/apache/sling/graphql/core/schema/DefaultSchemaProvider.java]
is an internal request to the path of that Resource with a `.GQLschema`
extension.
So that Resource should be setup with the appropriate `sling:resourceType` so
that the correct script or servlet is called to generate the schema.
If that information doesn't help, it would be useful if you can provide a
Sling-based example that reproduces your issue - and that would belong to a
different ticket.
> Extract a service to be able to execute GraphQL queries directly
> ----------------------------------------------------------------
>
> Key: SLING-9800
> URL: https://issues.apache.org/jira/browse/SLING-9800
> Project: Sling
> Issue Type: Improvement
> Components: GraphQL
> Reporter: Radu Cotescu
> Assignee: Radu Cotescu
> Priority: Major
> Fix For: GraphQL Core 0.0.8
>
>
> In the current implementation of the GraphQL Core bundle queries can only be
> executed via a GraphQL Servlet that needs to be configured or via server-side
> scripts. It would be good if the queries could also be executed directly,
> without the need for a request.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
