{
	"connector": {
		"class": "org.apache.camel.kafkaconnector.bean.CamelBeanSinkConnector",
		"artifactId": "camel-bean-kafka-connector",
		"groupId": "org.apache.camel.kafkaconnector",
		"id": "camel-bean-sink",
		"type": "sink",
		"version": "0.6.1"
	},
	"properties": {
		"camel.sink.path.beanName": {
			"name": "camel.sink.path.beanName",
			"description": "Sets the name of the bean to invoke",
			"priority": "HIGH",
			"required": "true"
		},
		"camel.sink.endpoint.cache": {
			"name": "camel.sink.endpoint.cache",
			"description": "Use scope option instead.",
			"priority": "LOW",
			"required": "false"
		},
		"camel.sink.endpoint.method": {
			"name": "camel.sink.endpoint.method",
			"description": "Sets the name of the method to invoke on the bean",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.scope": {
			"name": "camel.sink.endpoint.scope",
			"description": "Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using prototype scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry. One of: [Singleton] [Request] [Prototype]",
			"defaultValue": "\"Singleton\"",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.lazyStartProducer": {
			"name": "camel.sink.endpoint.lazyStartProducer",
			"description": "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.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.basicPropertyBinding": {
			"name": "camel.sink.endpoint.basicPropertyBinding",
			"description": "Whether the endpoint should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.parameters": {
			"name": "camel.sink.endpoint.parameters",
			"description": "Used for configuring additional properties on the bean",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.sink.endpoint.synchronous": {
			"name": "camel.sink.endpoint.synchronous",
			"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.bean.cache": {
			"name": "camel.component.bean.cache",
			"description": "Use singleton option instead.",
			"defaultValue": "\"true\"",
			"priority": "LOW",
			"required": "false"
		},
		"camel.component.bean.lazyStartProducer": {
			"name": "camel.component.bean.lazyStartProducer",
			"description": "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.",
			"defaultValue": "false",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.bean.scope": {
			"name": "camel.component.bean.scope",
			"description": "Scope of bean. When using singleton scope (default) the bean is created or looked up only once and reused for the lifetime of the endpoint. The bean should be thread-safe in case concurrent threads is calling the bean at the same time. When using request scope the bean is created or looked up once per request (exchange). This can be used if you want to store state on a bean while processing a request and you want to call the same bean instance multiple times while processing the request. The bean does not have to be thread-safe as the instance is only called from the same request. When using delegate scope, then the bean will be looked up or created per call. However in case of lookup then this is delegated to the bean registry such as Spring or CDI (if in use), which depends on their configuration can act as either singleton or prototype scope. so when using prototype then this depends on the delegated registry. One of: [Singleton] [Request] [Prototype]",
			"defaultValue": "\"Singleton\"",
			"priority": "MEDIUM",
			"required": "false"
		},
		"camel.component.bean.basicPropertyBinding": {
			"name": "camel.component.bean.basicPropertyBinding",
			"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
			"defaultValue": "false",
			"priority": "LOW",
			"required": "false"
		}
	}
}