Package org.allGraphQLCases.server

Class ReservedJavaKeywordAsObjectFieldController

java.lang.Object
org.allGraphQLCases.server.ReservedJavaKeywordAsObjectFieldController
@Controller @SchemaMapping(typeName="ReservedJavaKeywordAsObjectField") public class ReservedJavaKeywordAsObjectFieldController extends Object
Author:
generated by graphql-java-generator
See Also:

  • Field Details

  • Constructor Details

    • ReservedJavaKeywordAsObjectFieldController

      public ReservedJavaKeywordAsObjectFieldController()

  • Method Details

    • _if

      @SchemaMapping(field="if") public Object _if(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin, @Argument("new") String _new, @Argument("package") String _package, @Argument("private") String _private)
      This method loads the data for ${dataFetcher.graphQLType}.if. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      _new - The parameter that will receive the field argument of the same name for the current data to fetch
      _package - The parameter that will receive the field argument of the same name for the current data to fetch
      _private - The parameter that will receive the field argument of the same name for the current data to fetch
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="implements") public Object _implements(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.implements. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="import") public Object _import(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.import. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="instanceof") public Object _instanceof(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.instanceof. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="int") public Object _int(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.int. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="interface") public Object _interface(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.interface. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="long") public Object _long(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.long. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="native") public Object _native(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.native. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="new") public Object _new(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.new. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="package") public Object _package(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.package. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="private") public Object _private(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.private. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="protected") public Object _protected(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.protected. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="public") 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 ${dataFetcher.graphQLType}.public. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="return") public Object _return(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.return. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="short") public Object _short(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.short. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="static") public Object _static(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.static. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="strictfp") public Object _strictfp(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.strictfp. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="super") public Object _super(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.super. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="switch") public Object _switch(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.switch. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="synchronized") public Object _synchronized(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.synchronized. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="this") public Object _this(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.this. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="throw") public Object _throw(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.throw. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="throws") public Object _throws(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.throws. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="transient") public Object _transient(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.transient. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="try") public Object _try(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.try. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="void") public Object _void(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.void. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="volatile") public Object _volatile(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.volatile. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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

      @SchemaMapping(field="while") public Object _while(graphql.schema.DataFetchingEnvironment dataFetchingEnvironment, org.dataloader.DataLoader<UUID,STP_Human_STS> dataLoader, STP_ReservedJavaKeywordAsObjectField_STS origin)
      This method loads the data for ${dataFetcher.graphQLType}.while. It returns an Object: the data fetcher implementation may return any type that is accepted by a spring-graphql controller
      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 author attribute of the origin, which is an instance of {ObjectType {name:Post, fields:{Field{name:id, type:ID!, params:[]},Field{name:date, type:Date!, params:[]},Field{name:author, type:Member, params:[]},Field{name:publiclyAvailable, type:Boolean, params:[]},Field{name:title, type:String!, params:[]},Field{name:content, type:String!, params:[]},Field{name:authorId, type:ID, params:[]},Field{name:topicId, type:ID, params:[]}}, comments ""}. It depends on your data modle, but it typically contains the id to use in the query.
      Returns:
      It may return any value that is valid for a spring-graphql controller, annotated by the @SchemaMapping annotation
      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.