You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Temporary workaround is adding this code to remap some of the moved classes. The servlet expects a SimpleExecutionStrategy inside the graphql.execution package, so I created one that's extending the AsyncExecutionStrategy.
The TypeInfo class was also moved, so add that one too extending the class in its new location. This should allow bootstrapping to continue until the servlet is successfully patched.
If you're wondering why the AsyncExecutionStrategy was chosen in this example, see here: graphql-java/graphql-java#590. Quote:
SimpleExecutionStrategy is now SerialExecutionStrategy and is not used anymore by default, because it is blocking.
The new default strategy is AsyncExecutionStrategy for queries and AsyncSerialExecutionStrategy for mutations. Both are non blocking but are compatible to the old behaviour if DataFetcher are still blocking and not async.
Of course, you could easily extend from another strategy class if that makes sense for your use case. Code is in Kotlin.
Activity
jwalgemoed commentedon Sep 5, 2017
Temporary workaround is adding this code to remap some of the moved classes. The servlet expects a
SimpleExecutionStrategyinside thegraphql.executionpackage, so I created one that's extending theAsyncExecutionStrategy.The
TypeInfoclass was also moved, so add that one too extending the class in its new location. This should allow bootstrapping to continue until the servlet is successfully patched.If you're wondering why the
AsyncExecutionStrategywas chosen in this example, see here: graphql-java/graphql-java#590. Quote:Of course, you could easily extend from another strategy class if that makes sense for your use case. Code is in Kotlin.