anchor.diff:      }
   }
   ----
  -<1> The component configuration, that will be injected by the component framework
  -<2> The http client that we have created above. it will also be injected by the framework via the mapper constructor.
  -<3> We setup the base URL of our http client using the configuration url.
  -<4> As we will not split the http requests we return this mapper in the split method.
  -<5> We create a source that will perform the http request and return the search result.
  -
  -== The component source
  -Now we create the source that will perform the http request to the search api and convert the result to JsonObject records.
  +<1> The component configuration that is injected by the component framework
  +<2> The HTTP client created earlier in this tutorial. It is also injected by the framework via the mapper constructor.
  +<3> The base URL of the HTTP client is defined using the configuration URL.
  +<4> The mapper is returned in the split method because HTTP requests are not split.
  +<5> A source is created to perform the HTTP request and return the search result.
  +
  +== Defining the component source
  +Once the component logic implemented, you can create the source in charge of performing the HTTP request to the search API and converting the result to `JsonObject` records.
   [source,java,indent=0,subs="verbatim,quotes,attributes",]
   ----
   public class SearchSource implements Serializable {
  
positive.code:     }
  }
  ----
  <1> As This configuration class provide the authentication information. We can type it as `Datastore`,
  so that it can be validated using services (a kind of _test connection_ feature)
  or used by Talend studio or web application metadata.
  <2> This is the UI layout of this configuration.
  <3> We mark the password as `Credential` to that it can be handled as sensitive data in Talend Studio and web application.
  xref:tutorial-configuration-sensitive-data.adoc[Read more about sensitive data handling].
  <4> This method generate a basic authentication token using the username and the password. This token will be used
  to authenticate our http call to the Search API.
  
  Now that we have our data store configuration. that will provide us with the basic authentication token.
  We need to setup our data set configuration.
  i.e the search query that will define the records that our input component will provide.
  [source,java,indent=0,subs="verbatim,quotes,attributes",]
  ----
  @Data
  
negative.code:     private final String sortOrder;
  }
  ----
  <1> The configuration class is marked as a `DataSet`. xref:component-configuration.adoc#_marking_a_configuration_as_a_particular_type_of_data [Read more about configuration types].
  <2> `@GridLayout` defines the UI layout of this configuration.
  <3> A text area widget is bound to the *Search query* field. xref:gallery.adoc[See all the available widgets].
  <4> The `@Documentation` annotation is used to document the component (configuration in this scope).
  A Talend Component Kit Maven plugin can be used to generate the component documentation with all the configuration description and the default values.
  <5> A default value is defined for sorting the query result.
  
  Your component is configured. You can now create the component logic.
  
  == Defining the component mapper
  NOTE: Mappers defined with this tutorial don't implement the split part because HTTP calls are not split on many workers in this case.
  [source,java,indent=0,subs="verbatim,quotes,attributes",]
  ----
  @Version
  