[
https://issues.apache.org/jira/browse/SLING-10900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17695824#comment-17695824
]
Andreas Schaefer commented on SLING-10900:
------------------------------------------
After some help from the graphql-java team I was able to find a solution to
prevent the class loading issue by reverting back to the original class
loading. Branch
[https://github.com/apache/sling-org-apache-sling-graphql-core/tree/issue/SLING-10900-200]
does contain that fix.
That said this will still fail the Jenkins test as the graphql-java 20.0 is not
a valid Feature Model bundle. I hope that somewhere in April graphql-java team
will release 20.1 which should have all the fixes in place.
> Update graphl-java to version 17
> --------------------------------
>
> Key: SLING-10900
> URL: https://issues.apache.org/jira/browse/SLING-10900
> Project: Sling
> Issue Type: Improvement
> Components: GraphQL
> Reporter: Radu Cotescu
> Assignee: Andreas Schaefer
> Priority: Major
> Fix For: GraphQL Core 0.0.16
>
>
> {{graphql-java}} 17 brings a set of performance improvements [0] which could
> benefit the GraphQL Core bundle:
> * [2067|https://github.com/graphql-java/graphql-java/pull/2067] Support for
> Streams and Iterators
> * Dramatic performance improvements in GraphQLSchema building
> * Dramatic performance improvements in DataFetchingFieldSelectionSet
> * Dramatic performance improvements in large query validation
> [0] - https://github.com/graphql-java/graphql-java/releases/tag/v17.0
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
