[[chatscript-component]]
= ChatScript Component
//THIS FILE IS COPIED: EDIT THE SOURCE FILE:
:page-source: components/camel-chatscript/src/main/docs/chatscript-component.adoc
:docTitle: ChatScript
:artifactId: camel-chatscript
:description: Chat with a ChatScript Server.
:since: 3.0
:supportLevel: Stable
:component-header: Only producer is supported
include::{cq-version}@camel-quarkus:ROOT:partial$reference/components/chatscript.adoc[opts=optional]

*Since Camel {since}*

*{component-header}*

The ChatScript component allows you to interact with ChatScript Server and have conversations. This component is stateless and relies on ChatScript to maintain chat history.

Original ChatScript is available here : https://github.com/bwilcox-1234/ChatScript

This component expects a JSON having the following fields:
{
username:
botname:
body:
}

Refer ChatScriptMessage.java and samples  

Maven users will need to add the following dependency to their `pom.xml`
for this component:

[source,xml]
------------------------------------------------------------
<dependency>
    <groupId>org.apache.camel</groupId>
      <artifactId>camel-chatscript</artifactId>
    <version>x.x.x</version>
    <!-- use the same version as your Camel core version -->
</dependency>
------------------------------------------------------------

== URI format
[source,java]
-------------------------------------------------------------------------------------------------------------------------
ChatScript:host:[port]/botName[?options]
-------------------------------------------------------------------------------------------------------------------------

== Options

// component options: START
The ChatScript component supports 2 options, which are listed below.



[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean
| *autowiredEnabled* (advanced) | Whether autowiring is enabled. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc. | true | boolean
|===
// component options: END

// endpoint options: START
The ChatScript endpoint is configured using URI syntax:

----
chatscript:host:port/botName
----

with the following path and query parameters:

=== Path Parameters (3 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *host* | *Required* Hostname or IP of the server on which CS server is running |  | String
| *port* | Port on which ChatScript is listening to | 1024 | int
| *botName* | *Required* Name of the Bot in CS to converse with |  | String
|===


=== Query Parameters (3 parameters):


[width="100%",cols="2,5,^1,2",options="header"]
|===
| Name | Description | Default | Type
| *chatUserName* (producer) | Username who initializes the CS conversation. To be set when chat is initialized from camel route |  | String
| *lazyStartProducer* (producer) | Whether the producer should be started lazy (on the first message). By starting lazy you can use this to allow CamelContext and routes to startup in situations where a producer may otherwise fail during starting and cause the route to fail being started. By deferring this startup to be lazy then the startup failure can be handled during routing messages via Camel's routing error handlers. Beware that when the first message is processed then creating and starting the producer may take a little time and prolong the total processing time of the processing. | false | boolean
| *resetChat* (producer) | Issues :reset command to start a new conversation everytime | false | boolean
|===
// endpoint options: END


include::{page-component-version}@camel-spring-boot::page$chatscript-starter.adoc[]
