Package org.allGraphQLCases.server

Interface DataFetchersDelegateReservedJavaKeywordAsObjectField

All Known Implementing Classes:
DataFetchersDelegateReservedJavaKeywordAsObjectFieldImpl
public interface DataFetchersDelegateReservedJavaKeywordAsObjectField
This interface contains the fata fetchers that are delegated in the bean that the implementation has to provide, when fetching fields for the ReservedJavaKeywordAsObjectField GraphQL type, as defined in the provided GraphQL schema. Please read the wiki server page for more information on this.
Author:
generated by graphql-java-generator
See Also:

  • Method Details

    • _if

      Object _if(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin, String _new, String _package, String _private)
      This method loads the data for ReservedJavaKeywordAsObjectField.if. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the if attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      new - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      package - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      private - The input parameter sent in the query by the GraphQL consumer, as defined in the GraphQL schema.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _implements

      Object _implements(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.implements. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the implements attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _import

      Object _import(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.import. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the import attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _instanceof

      Object _instanceof(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.instanceof. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the instanceof attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _int

      Object _int(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.int. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the int attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _interface

      Object _interface(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.interface. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the interface attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _long

      Object _long(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.long. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the long attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _native

      Object _native(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.native. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the native attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _new

      Object _new(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.new. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the new attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _package

      Object _package(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.package. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the package attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _private

      Object _private(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.private. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the private attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _protected

      Object _protected(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.protected. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the protected attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _public

      Object _public(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.public. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the public attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _return

      Object _return(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.return. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the return attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _short

      Object _short(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.short. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the short attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _static

      Object _static(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.static. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the static attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _strictfp

      Object _strictfp(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.strictfp. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the strictfp attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _super

      Object _super(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.super. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the super attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _switch

      Object _switch(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.switch. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the switch attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _synchronized

      Object _synchronized(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.synchronized. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the synchronized attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _this

      Object _this(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.this. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the this attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _throw

      Object _throw(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.throw. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the throw attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _throws

      Object _throws(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.throws. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the throws attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _transient

      Object _transient(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.transient. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the transient attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _try

      Object _try(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.try. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the try attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _void

      Object _void(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.void. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the void attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _volatile

      Object _volatile(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.volatile. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the volatile attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.

    • _while

      Object _while(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ReservedJavaKeywordAsObjectField.while. It may return whatever is accepted by the Spring Controller, that is:
      • A resolved value of any type (typically, a org.allGraphQLCases.server.STP_Human_STS)
      • Mono and Flux for asynchronous value(s). Supported for controller methods and for any DataFetcher as described in Reactive DataFetcher. This would typically be a Mono<org.allGraphQLCases.server.STP_Human_STS> or a Flux<org.allGraphQLCases.server.STP_Human_STS>
      • Kotlin coroutine and Flow are adapted to Mono and Flux
      • java.util.concurrent.Callable to have the value(s) produced asynchronously. For this to work, AnnotatedControllerConfigurer must be configured with an Executor. This would typically by a Callable<org.allGraphQLCases.server.STP_Human_STS>
      As a complement to the spring-graphql documentation, you may also return:
      • A CompletableFuture<?>, for instance CompletableFuture<org.allGraphQLCases.server.STP_Human_STS>. This allows to use graphql-java java-dataloader to highly optimize the number of requests to the server. The principle is this one: The data loader collects all the data to load, avoid to load several times the same data, and allows parallel execution of the queries, if multiple queries are to be run.
      • A Publisher (instead of a Flux), for Subscription for instance
      Parameters:
      dataFetchingEnvironment - The GraphQL DataFetchingEnvironment. It gives you access to the full GraphQL context for this DataFetcher
      dataLoader - The DataLoader allows to load several data in one query. It allows to solve the (n+1) queries issues, and greatly optimizes the response time.
      You'll find more informations here: https://github.com/graphql-java/java-dataloader
      origin - The object from which the field is fetch. In other word: the aim of this data fetcher is to fetch the while attribute of the origin, which is an instance of {ObjectType {name:ReservedJavaKeywordAsObjectField, fields:{Field{name:if, type:Human, params:[new:String,package:String,private:String]},Field{name:implements, type:Human, params:[]},Field{name:import, type:Human, params:[]},Field{name:instanceof, type:Human, params:[]},Field{name:int, type:Human, params:[]},Field{name:interface, type:Human, params:[]},Field{name:long, type:Human, params:[]},Field{name:native, type:Human, params:[]},Field{name:new, type:Human, params:[]},Field{name:package, type:Human, params:[]},Field{name:private, type:Human, params:[]},Field{name:protected, type:Human, params:[]},Field{name:public, type:Human, params:[]},Field{name:return, type:Human, params:[]},Field{name:short, type:Human, params:[]},Field{name:static, type:Human, params:[]},Field{name:strictfp, type:Human, params:[]},Field{name:super, type:Human, params:[]},Field{name:switch, type:Human, params:[]},Field{name:synchronized, type:Human, params:[]},Field{name:this, type:Human, params:[]},Field{name:throw, type:Human, params:[]},Field{name:throws, type:Human, params:[]},Field{name:transient, type:Human, params:[]},Field{name:try, type:Human, params:[]},Field{name:void, type:Human, params:[]},Field{name:volatile, type:Human, params:[]},Field{name:while, type:Human, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Throws:
      NoSuchElementException - This method may return a NoSuchElementException exception. In this case, the exception is trapped by the calling method, and the return is consider as null. This allows to use the Optional.get() method directly, without caring of whether or not there is a value. The generated code will take care of the NoSuchElementException exception.