release version 1.10.0

This commit is contained in:
2024-10-07 18:42:55 +03:00
parent 2034182607
commit a5088587f7
1501 changed files with 28818 additions and 59966 deletions

View File

@ -3,7 +3,7 @@
<parent>
<groupId>ru.entaxy.esb.platform.runtime.core.objects-implementations</groupId>
<artifactId>connection-implementation</artifactId>
<version>1.9.0</version>
<version>1.10.0</version>
</parent>
<groupId>ru.entaxy.esb.platform.runtime.core.objects-implementations.connection-implementation</groupId>
<artifactId>connection-producing</artifactId>

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* connection-producing
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -10,6 +10,31 @@
"modeSupported": "BOTH"
},
"fields": {
"isPlatform": {
"type": "boolean",
"required": true,
"isHidden": true,
"immutable": true,
"defaultValue": false,
"@UI": {
"transmitAlways": true
}
},
"##publish": {
"type": "Map",
"required": true,
"isHidden": true,
"defaultValue":{
"platform": {
"@CALCULATED": {
"expression": "${properties.isPlatform}",
"lazy": false,
"allowObjects": false
}
}
}
},
"##publishRelation": {
"type": "String",
"isHidden": true,
@ -30,7 +55,8 @@
"fields": {
"##publishRelation": {
"@SCOPED": ["private"]
}
},
"isPlatform": {}
},
"config": {
"configurable": false

View File

@ -3,7 +3,7 @@
<parent>
<groupId>ru.entaxy.esb.platform.runtime.core</groupId>
<artifactId>objects-implementations</artifactId>
<version>1.9.0</version>
<version>1.10.0</version>
</parent>
<groupId>ru.entaxy.esb.platform.runtime.core.objects-implementations</groupId>
<artifactId>connection-implementation</artifactId>

View File

@ -4,7 +4,7 @@
<parent>
<groupId>ru.entaxy.esb.platform.runtime.core.objects-implementations</groupId>
<artifactId>connection-implementation</artifactId>
<version>1.9.0</version>
<version>1.10.0</version>
</parent>
<groupId>ru.entaxy.esb.platform.runtime.core.objects-implementations.connection-implementation</groupId>
<artifactId>standard-connections-pack</artifactId>

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* file-adapter
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* file-adapter
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property
@ -26,11 +26,9 @@
package ru.entaxy.platform.runtime.connections.ftp;
import org.apache.camel.ExtendedCamelContext;
import org.apache.camel.component.file.remote.FtpComponent;
import org.apache.camel.component.file.GenericFileEndpoint;
import org.apache.camel.component.file.remote.FtpComponent;
import org.apache.camel.spi.PropertyConfigurer;
import org.apache.camel.util.ObjectHelper;
import org.apache.camel.util.StringHelper;
import org.apache.commons.net.ftp.FTPFile;
import ru.entaxy.platform.base.support.CommonUtils;
@ -38,53 +36,95 @@ import java.util.Map;
public class FtpConnectionComponent extends FtpComponent {
public static final String CONNECTION_STRING_PLACEHOLDER = "CONNECTION_STRING_PLACEHOLDER";
protected String connectionString = "";
private static final String COMPONENT_CONFIGURER = "ftp-component-configurer";
private static final String ENDPOINT_CONFIGURER = "ftp-endpoint-configurer";
private static final String PATH_PLACEHOLDER = "PATH_PLACEHOLDER";
@Override
protected GenericFileEndpoint<FTPFile> createEndpoint(String uri, String remaining, Map<String, Object> parameters)
throws Exception {
protected String username = "";
protected String password = "";
protected String host = "";
protected String port = "";
protected String directoryName = "";
if (CommonUtils.isValid(connectionString)) {
uri = uri.replace(CONNECTION_STRING_PLACEHOLDER, connectionString);
remaining = connectionString;
}
private volatile PropertyConfigurer componentPropertyConfigurerLocal;
private volatile PropertyConfigurer endpointPropertyConfigurerLocal;
String schema = uri.substring(0, uri.indexOf(":"));
String newUri = uri.replace(schema+":", "ftp:");
@Override
protected void doBuild() {
log.debug("CREATING ENDPOINT FOR [{}]", uri);
return super.createEndpoint(newUri, remaining, parameters);
}
componentPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver()
.resolvePropertyConfigurer(COMPONENT_CONFIGURER, getCamelContext());
log.debug("componentPropertyConfigurerLocal: {}", componentPropertyConfigurerLocal);
protected void doBuild() throws Exception {
String name = "ftp";
// just grab first scheme name if the component has scheme alias (eg http,https)
if (name.contains(",")) {
name = StringHelper.before(name, ",");
}
final String componentConfigurerName = name + "-component-configurer";
componentPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver().resolvePropertyConfigurer(componentConfigurerName, getCamelContext());
final String endpointConfigurerName = name + "-endpoint-configurer";
endpointPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver().resolvePropertyConfigurer(endpointConfigurerName, getCamelContext());
}
@Override
public PropertyConfigurer getComponentPropertyConfigurer() {
return componentPropertyConfigurerLocal;
}
endpointPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver()
.resolvePropertyConfigurer(ENDPOINT_CONFIGURER, getCamelContext());
log.debug("endpointPropertyConfigurerLocal: {}", endpointPropertyConfigurerLocal);
}
private volatile PropertyConfigurer componentPropertyConfigurerLocal;
@Override
public PropertyConfigurer getEndpointPropertyConfigurer() {
return endpointPropertyConfigurerLocal;
}
private volatile PropertyConfigurer endpointPropertyConfigurerLocal;
protected GenericFileEndpoint<FTPFile> createEndpoint(String uri, String remaining, Map<String, Object> parameters)
throws Exception {
public String getConnectionString() {
return connectionString;
}
// doBuild method called to force configurer initialization (doBuild not invoked in some scenario)
doBuild();
uri = uri.replace(PATH_PLACEHOLDER, buildPath());
log.debug("CREATING ENDPOINT FOR [{}]", uri);
if (CommonUtils.isValid(username)) {
parameters.put("username", username);
}
if (CommonUtils.isValid(password)) {
parameters.put("password", password);
}
public void setConnectionString(String connectionString) {
this.connectionString = connectionString;
}
return super.createEndpoint(uri, remaining, parameters);
}
private String buildPath() {
StringBuilder path = new StringBuilder();
if (CommonUtils.isValid(host)) {
path.append(host.trim());
}
if (CommonUtils.isValid(port)) {
path.append(":");
path.append(port.trim());
}
if (CommonUtils.isValid(directoryName)) {
if (!directoryName.startsWith("/")) {
path.append("/");
}
path.append(directoryName.trim());
}
return path.toString();
}
public void setUsername(String username) {
this.username = username;
}
public void setPassword(String password) {
this.password = password;
}
public void setHost(String host) {
this.host = host;
}
public void setPort(String port) {
this.port = port;
}
public void setDirectoryName(String directoryName) {
this.directoryName = directoryName;
}
@Override
public PropertyConfigurer getComponentPropertyConfigurer() {
return componentPropertyConfigurerLocal;
}
@Override
public PropertyConfigurer getEndpointPropertyConfigurer() {
return endpointPropertyConfigurerLocal;
}
}

View File

@ -2,7 +2,7 @@
* ~~~~~~licensing~~~~~~
* file-adapter
* ==========
* Copyright (C) 2020 - 2023 EmDev LLC
* Copyright (C) 2020 - 2024 EmDev LLC
* ==========
* You may not use this file except in accordance with the License Terms of the Copyright
* Holder located at: https://entaxy.ru/eula . All copyrights, all intellectual property
@ -30,60 +30,102 @@ import org.apache.camel.component.file.GenericFileEndpoint;
import org.apache.camel.component.file.remote.SftpComponent;
import org.apache.camel.component.file.remote.SftpRemoteFile;
import org.apache.camel.spi.PropertyConfigurer;
import org.apache.camel.util.StringHelper;
import ru.entaxy.platform.base.support.CommonUtils;
import java.util.Map;
public class SftpConnectionComponent extends SftpComponent {
public static final String CONNECTION_STRING_PLACEHOLDER = "CONNECTION_STRING_PLACEHOLDER";
protected String connectionString = "";
private static final String COMPONENT_CONFIGURER = "sftp-component-configurer";
private static final String ENDPOINT_CONFIGURER = "sftp-endpoint-configurer";
private static final String PATH_PLACEHOLDER = "PATH_PLACEHOLDER";
@Override
protected GenericFileEndpoint<SftpRemoteFile> createEndpoint(String uri, String remaining, Map<String, Object> parameters)
throws Exception {
protected String username = "";
protected String password = "";
protected String host = "";
protected String port = "";
protected String directoryName = "";
if (CommonUtils.isValid(connectionString)) {
uri = uri.replace(CONNECTION_STRING_PLACEHOLDER, connectionString);
remaining = connectionString;
}
private volatile PropertyConfigurer componentPropertyConfigurerLocal;
private volatile PropertyConfigurer endpointPropertyConfigurerLocal;
String schema = uri.substring(0, uri.indexOf(":"));
String newUri = uri.replace(schema+":", "sftp:");
@Override
protected void doBuild() {
log.debug("CREATING ENDPOINT FOR [{}]", uri);
return super.createEndpoint(newUri, remaining, parameters);
}
componentPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver()
.resolvePropertyConfigurer(COMPONENT_CONFIGURER, getCamelContext());
log.debug("componentPropertyConfigurerLocal: {}", componentPropertyConfigurerLocal);
protected void doBuild() throws Exception {
String name = "sftp";
// just grab first scheme name if the component has scheme alias (eg http,https)
if (name.contains(",")) {
name = StringHelper.before(name, ",");
}
final String componentConfigurerName = name + "-component-configurer";
componentPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver().resolvePropertyConfigurer(componentConfigurerName, getCamelContext());
final String endpointConfigurerName = name + "-endpoint-configurer";
endpointPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver().resolvePropertyConfigurer(endpointConfigurerName, getCamelContext());
}
@Override
public PropertyConfigurer getComponentPropertyConfigurer() {
return componentPropertyConfigurerLocal;
}
endpointPropertyConfigurerLocal = getCamelContext().adapt(ExtendedCamelContext.class).getConfigurerResolver()
.resolvePropertyConfigurer(ENDPOINT_CONFIGURER, getCamelContext());
log.debug("endpointPropertyConfigurerLocal: {}", endpointPropertyConfigurerLocal);
}
private volatile PropertyConfigurer componentPropertyConfigurerLocal;
@Override
public PropertyConfigurer getEndpointPropertyConfigurer() {
return endpointPropertyConfigurerLocal;
}
private volatile PropertyConfigurer endpointPropertyConfigurerLocal;
protected GenericFileEndpoint<SftpRemoteFile> createEndpoint(String uri, String remaining,
Map<String, Object> parameters)
throws Exception {
public String getConnectionString() {
return connectionString;
}
// doBuild method called to force configurer initialization (doBuild not invoked in some scenario)
doBuild();
uri = uri.replace(PATH_PLACEHOLDER, buildPath());
log.debug("CREATING ENDPOINT FOR [{}]", uri);
if (CommonUtils.isValid(username)) {
parameters.put("username", username);
}
if (CommonUtils.isValid(password)) {
parameters.put("password", password);
}
public void setConnectionString(String connectionString) {
this.connectionString = connectionString;
}
return super.createEndpoint(uri, remaining, parameters);
}
private String buildPath() {
StringBuilder path = new StringBuilder();
if (CommonUtils.isValid(host)) {
path.append(host.trim());
}
if (CommonUtils.isValid(port)) {
path.append(":");
path.append(port.trim());
}
if (CommonUtils.isValid(directoryName)) {
if (!directoryName.startsWith("/")) {
path.append("/");
}
path.append(directoryName.trim());
}
return path.toString();
}
public void setUsername(String username) {
this.username = username;
}
public void setPassword(String password) {
this.password = password;
}
public void setHost(String host) {
this.host = host;
}
public void setPort(String port) {
this.port = port;
}
public void setDirectoryName(String directoryName) {
this.directoryName = directoryName;
}
@Override
public PropertyConfigurer getComponentPropertyConfigurer() {
return componentPropertyConfigurerLocal;
}
@Override
public PropertyConfigurer getEndpointPropertyConfigurer() {
return endpointPropertyConfigurerLocal;
}
}

View File

@ -6,7 +6,8 @@
"isAbstract": false,
"camelOriginComponent": "jms",
"label": "messaging,artemis",
"description": "Sent and receive messages to/from a JMS Queue or Topic.",
"description": "This component allows messages to be sent to (or consumed from) a JMS Queue or Topic. It uses Springs JMS support for declarative transactions, including Springs JmsTemplate for sending and a MessageListenerContainer for consuming. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"displayName": "ARTEMIS",
"camelOrigin": "camel-jms",
"camelOriginJavaType": "org.apache.camel.component.jms.JmsComponent"
},
@ -14,7 +15,7 @@
"fields": {
"clientId": {
"displayName": "Client Id",
"description": "Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead.",
"description": "Sets the JMS client ID to use. Note that this value, if specified, must be unique and can only be used by a single JMS connection instance. It is typically only required for durable topic subscriptions. If using Apache ActiveMQ you may prefer to use Virtual Topics instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"required": false,
@ -42,7 +43,7 @@
},
"disableReplyTo": {
"displayName": "Disable Reply To",
"description": "Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another.",
"description": "Specifies whether Camel ignores the JMSReplyTo header in messages. If true, Camel does not send a reply back to the destination specified in the JMSReplyTo header. You can use this option if you want Camel to consume from a route and you do not want Camel to automatically send back a reply message because another component in your code handles the reply message. You can also use this option if you want to use Camel as a proxy between different message brokers and you want to route message from one system to another. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"required": false,
@ -71,7 +72,7 @@
},
"durableSubscriptionName": {
"displayName": "Durable Subscription Name",
"description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well.",
"description": "The durable subscriber name for specifying durable topic subscriptions. The clientId option must be configured as well. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"required": false,
@ -99,7 +100,7 @@
},
"jmsMessageType": {
"displayName": "Jms Message Type",
"description": "Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it.",
"description": "Allows you to force the use of a specific javax.jms.Message implementation for sending JMS messages. Possible values are: Bytes, Map, Object, Stream, Text. By default, Camel would determine which JMS message type to use from the In body type. This option allows you to specify it. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "object",
"required": false,
@ -137,7 +138,7 @@
},
"testConnectionOnStartup": {
"displayName": "Test Connection On Startup",
"description": "Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well.",
"description": "Specifies whether to test the connection on startup. This ensures that when Camel starts that all the JMS consumers have a valid connection to the JMS broker. If a connection cannot be granted then Camel throws an exception on startup. This ensures that Camel is not started with failed connections. The JMS producers is tested as well. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"required": false,
@ -166,7 +167,7 @@
},
"acknowledgementModeName": {
"displayName": "Acknowledgement Mode Name",
"description": "The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE",
"description": "The JMS acknowledgement name, which is one of: SESSION_TRANSACTED, CLIENT_ACKNOWLEDGE, AUTO_ACKNOWLEDGE, DUPS_OK_ACKNOWLEDGE. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"required": false,
@ -204,7 +205,7 @@
},
"asyncConsumer": {
"displayName": "Async Consumer",
"description": "Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer\u003dtrue does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions).",
"description": "Whether the JmsConsumer processes the Exchange asynchronously. If enabled then the JmsConsumer may pickup the next message from the JMS queue, while the previous message is being processed asynchronously (by the Asynchronous Routing Engine). This means that messages may be processed not 100% strictly in order. If disabled (as default) then the Exchange is fully processed before the JmsConsumer will pickup the next message from the JMS queue. Note if transacted has been enabled, then asyncConsumer\u003dtrue does not run asynchronously, as transaction must be executed synchronously (Camel 3.0 may support async transactions). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -233,7 +234,7 @@
},
"autoStartup": {
"displayName": "Auto Startup",
"description": "Specifies whether the consumer container should auto-startup.",
"description": "Specifies whether the consumer container should auto-startup. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -262,7 +263,7 @@
},
"cacheLevel": {
"displayName": "Cache Level",
"description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details.",
"description": "Sets the cache level by ID for the underlying JMS resources. See cacheLevelName option for more details. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "number",
"required": false,
@ -290,7 +291,7 @@
},
"cacheLevelName": {
"displayName": "Cache Level Name",
"description": "Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information.",
"description": "Sets the cache level by name for the underlying JMS resources. Possible values are: CACHE_AUTO, CACHE_CONNECTION, CACHE_CONSUMER, CACHE_NONE, and CACHE_SESSION. The default setting is CACHE_AUTO. See the Spring documentation and Transactions Cache Levels for more information. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"required": false,
@ -329,7 +330,7 @@
},
"concurrentConsumers": {
"displayName": "Concurrent Consumers",
"description": "Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.",
"description": "Specifies the default number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "number",
"required": false,
@ -358,7 +359,7 @@
},
"maxConcurrentConsumers": {
"displayName": "Max Concurrent Consumers",
"description": "Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener.",
"description": "Specifies the maximum number of concurrent consumers when consuming from JMS (not for request/reply over JMS). See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. When doing request/reply over JMS then the option replyToMaxConcurrentConsumers is used to control number of concurrent consumers on the reply message listener. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "number",
"required": false,
@ -386,7 +387,7 @@
},
"replyTo": {
"displayName": "Reply To",
"description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo().",
"description": "Provides an explicit ReplyTo destination, which overrides any incoming value of Message.getJMSReplyTo(). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"required": false,
@ -414,7 +415,7 @@
},
"replyToDeliveryPersistent": {
"displayName": "Reply To Delivery Persistent",
"description": "Specifies whether to use persistent delivery by default for replies.",
"description": "Specifies whether to use persistent delivery by default for replies. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -443,7 +444,7 @@
},
"selector": {
"displayName": "Selector",
"description": "Sets the JMS selector to use",
"description": "Sets the JMS selector to use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"required": false,
@ -471,7 +472,7 @@
},
"subscriptionDurable": {
"displayName": "Subscription Durable",
"description": "Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well.",
"description": "Set whether to make the subscription durable. The durable subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a durable subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -500,7 +501,7 @@
},
"subscriptionName": {
"displayName": "Subscription Name",
"description": "Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client\u0027s JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0).",
"description": "Set the name of a subscription to create. To be applied in case of a topic (pub-sub domain) with a shared or durable subscription. The subscription name needs to be unique within this client\u0027s JMS client id. Default is the class name of the specified message listener. Note: Only 1 concurrent consumer (which is the default of this message listener container) is allowed for each subscription, except for a shared subscription (which requires JMS 2.0). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"required": false,
@ -528,7 +529,7 @@
},
"subscriptionShared": {
"displayName": "Subscription Shared",
"description": "Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker.",
"description": "Set whether to make the subscription shared. The shared subscription name to be used can be specified through the subscriptionName property. Default is false. Set this to true to register a shared subscription, typically in combination with a subscriptionName value (unless your message listener class name is good enough as subscription name). Note that shared subscriptions may also be durable, so this flag can (and often will) be combined with subscriptionDurable as well. Only makes sense when listening to a topic (pub-sub domain), therefore this method switches the pubSubDomain flag as well. Requires a JMS 2.0 compatible message broker. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -557,7 +558,7 @@
},
"acceptMessagesWhileStopping": {
"displayName": "Accept Messages While Stopping",
"description": "Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option.",
"description": "Specifies whether the consumer accept messages while it is stopping. You may consider enabling this option, if you start and stop JMS routes at runtime, while there are still messages enqueued on the queue. If this option is false, and you stop the JMS route, then messages may be rejected, and the JMS broker would have to attempt redeliveries, which yet again may be rejected, and eventually the message may be moved at a dead letter queue on the JMS broker. To avoid this its recommended to enable this option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"required": false,
@ -586,7 +587,7 @@
},
"allowReplyManagerQuickStop": {
"displayName": "Allow Reply Manager Quick Stop",
"description": "Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag.",
"description": "Whether the DefaultMessageListenerContainer used in the reply managers for request-reply messaging allow the DefaultMessageListenerContainer.runningAllowed flag to quick stop in case JmsConfiguration#isAcceptMessagesWhileStopping is enabled, and org.apache.camel.CamelContext is currently being stopped. This quick stop ability is enabled by default in the regular JMS consumers but to enable for reply managers you must enable this flag. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"required": false,
@ -615,7 +616,7 @@
},
"consumerType": {
"displayName": "Consumer Type",
"description": "The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use.",
"description": "The consumer type to use, which can be one of: Simple, Default, or Custom. The consumer type determines which Spring JMS listener to use. Default will use org.springframework.jms.listener.DefaultMessageListenerContainer, Simple will use org.springframework.jms.listener.SimpleMessageListenerContainer. When Custom is specified, the MessageListenerContainerFactory defined by the messageListenerContainerFactory option will determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"required": false,
@ -652,7 +653,7 @@
},
"defaultTaskExecutorType": {
"displayName": "Default Task Executor Type",
"description": "Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring\u0027s SimpleAsyncTaskExecutor) or ThreadPool (uses Spring\u0027s ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers.",
"description": "Specifies what default TaskExecutor type to use in the DefaultMessageListenerContainer, for both consumer endpoints and the ReplyTo consumer of producer endpoints. Possible values: SimpleAsync (uses Spring\u0027s SimpleAsyncTaskExecutor) or ThreadPool (uses Spring\u0027s ThreadPoolTaskExecutor with optimal values - cached threadpool-like). If not set, it defaults to the previous behaviour, which uses a cached thread pool for consumer endpoints and SimpleAsync for reply consumers. The use of ThreadPool is recommended to reduce thread trash in elastic configurations with dynamically increasing and decreasing concurrent consumers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"required": false,
@ -687,7 +688,7 @@
},
"eagerLoadingOfProperties": {
"displayName": "Eager Loading Of Properties",
"description": "Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody.",
"description": "Enables eager loading of JMS properties and payload as soon as a message is loaded which generally is inefficient as the JMS properties may not be required but sometimes can catch early any issues with the underlying JMS provider and the use of JMS properties. See also the option eagerPoisonBody. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"required": false,
@ -716,7 +717,7 @@
},
"eagerPoisonBody": {
"displayName": "Eager Poison Body",
"description": "If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody\u003dfalse. See also the option eagerLoadingOfProperties.",
"description": "If eagerLoadingOfProperties is enabled and the JMS message payload (JMS body or JMS properties) is poison (cannot be read/mapped), then set this text as the message body instead so the message can be processed (the cause of the poison are already stored as exception on the Exchange). This can be turned off by setting eagerPoisonBody\u003dfalse. See also the option eagerLoadingOfProperties. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"required": false,
@ -745,7 +746,7 @@
},
"exposeListenerSession": {
"displayName": "Expose Listener Session",
"description": "Specifies whether the listener session should be exposed when consuming messages.",
"description": "Specifies whether the listener session should be exposed when consuming messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"required": false,
@ -774,7 +775,7 @@
},
"replyToSameDestinationAllowed": {
"displayName": "Reply To Same Destination Allowed",
"description": "Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself.",
"description": "Whether a JMS consumer is allowed to send a reply message to the same destination that the consumer is using to consume from. This prevents an endless loop by consuming and sending back the same message to itself. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"required": false,
@ -803,7 +804,7 @@
},
"taskExecutor": {
"displayName": "Task Executor",
"description": "Allows you to specify a custom task executor for consuming messages.",
"description": "Allows you to specify a custom task executor for consuming messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"required": false,
@ -831,7 +832,7 @@
},
"deliveryDelay": {
"displayName": "Delivery Delay",
"description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker.",
"description": "Sets delivery delay to use for send calls for JMS. This option requires JMS 2.0 compliant broker. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -860,7 +861,7 @@
},
"deliveryMode": {
"displayName": "Delivery Mode",
"description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT \u003d 1 and PERSISTENT \u003d 2.",
"description": "Specifies the delivery mode to be used. Possibles values are those defined by javax.jms.DeliveryMode. NON_PERSISTENT \u003d 1 and PERSISTENT \u003d 2. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -895,7 +896,7 @@
},
"deliveryPersistent": {
"displayName": "Delivery Persistent",
"description": "Specifies whether persistent delivery is used by default.",
"description": "Specifies whether persistent delivery is used by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -924,7 +925,7 @@
},
"explicitQosEnabled": {
"displayName": "Explicit Qos Enabled",
"description": "Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring\u0027s JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers.",
"description": "Set if the deliveryMode, priority or timeToLive qualities of service should be used when sending messages. This option is based on Spring\u0027s JmsTemplate. The deliveryMode, priority and timeToLive options are applied to the current endpoint. This contrasts with the preserveMessageQos option, which operates at message granularity, reading QoS properties exclusively from the Camel In message headers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -953,7 +954,7 @@
},
"formatDateHeadersToIso8601": {
"displayName": "Format Date Headers To Iso8601",
"description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard.",
"description": "Sets whether JMS date properties should be formatted according to the ISO 8601 standard. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -982,7 +983,7 @@
},
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -1007,7 +1008,7 @@
},
"preserveMessageQos": {
"displayName": "Preserve Message Qos",
"description": "Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header.",
"description": "Set to true, if you want to send message using the QoS settings specified on the message, instead of the QoS settings on the JMS endpoint. The following three headers are considered JMSPriority, JMSDeliveryMode, and JMSExpiration. You can provide all or only some of them. If not provided, Camel will fall back to use the values from the endpoint instead. So, when using this option, the headers override the values from the endpoint. The explicitQosEnabled option, by contrast, will only use options set on the endpoint, and not values from the message header. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -1036,7 +1037,7 @@
},
"priority": {
"displayName": "Priority",
"description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect.",
"description": "Values greater than 1 specify the message priority when sending (where 0 is the lowest priority and 9 is the highest). The explicitQosEnabled option must also be enabled in order for this option to have any effect. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -1046,15 +1047,15 @@
"@TYPEINFO": {
"type": "enum",
"values": [
"1",
"2",
"3",
"4",
"5",
"6",
"7",
"8",
"9"
1,
2,
3,
4,
5,
6,
7,
8,
9
]
},
"##origin": "camel",
@ -1079,7 +1080,7 @@
},
"replyToConcurrentConsumers": {
"displayName": "Reply To Concurrent Consumers",
"description": "Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.",
"description": "Specifies the default number of concurrent consumers when doing request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -1108,7 +1109,7 @@
},
"replyToMaxConcurrentConsumers": {
"displayName": "Reply To Max Concurrent Consumers",
"description": "Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads.",
"description": "Specifies the maximum number of concurrent consumers when using request/reply over JMS. See also the maxMessagesPerTask option to control dynamic scaling up/down of threads. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -1136,7 +1137,7 @@
},
"replyToOnTimeoutMaxConcurrentConsumers": {
"displayName": "Reply To On Timeout Max Concurrent Consumers",
"description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS.",
"description": "Specifies the maximum number of concurrent consumers for continue routing when timeout occurred when using request/reply over JMS. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -1165,7 +1166,7 @@
},
"replyToOverride": {
"displayName": "Reply To Override",
"description": "Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination.",
"description": "Provides an explicit ReplyTo destination in the JMS message, which overrides the setting of replyTo. It is useful if you want to forward the message to a remote Queue and receive the reply message from the ReplyTo destination. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"required": false,
@ -1193,7 +1194,7 @@
},
"replyToType": {
"displayName": "Reply To Type",
"description": "Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive.",
"description": "Allows for explicitly specifying which kind of strategy to use for replyTo queues when doing request/reply over JMS. Possible values are: Temporary, Shared, or Exclusive. By default Camel will use temporary queues. However if replyTo has been configured, then Shared is used by default. This option allows you to use exclusive queues instead of shared ones. See Camel JMS documentation for more details, and especially the notes about the implications if running in a clustered environment, and the fact that Shared reply queues has lower performance than its alternatives Temporary and Exclusive. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "object",
"required": false,
@ -1229,7 +1230,7 @@
},
"requestTimeout": {
"displayName": "Request Timeout",
"description": "The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option.",
"description": "The timeout for waiting for a reply when using the InOut Exchange Pattern (in milliseconds). The default is 20 seconds. You can include the header CamelJmsRequestTimeout to override this endpoint configured timeout value, and thus have per message individual timeout values. See also the requestTimeoutCheckerInterval option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "duration",
"required": false,
@ -1258,7 +1259,7 @@
},
"timeToLive": {
"displayName": "Time To Live",
"description": "When sending messages, specifies the time-to-live of the message (in milliseconds).",
"description": "When sending messages, specifies the time-to-live of the message (in milliseconds). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer",
"type": "number",
"required": false,
@ -1287,7 +1288,7 @@
},
"allowAdditionalHeaders": {
"displayName": "Allow Additional Headers",
"description": "This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching.",
"description": "This option is used to allow additional headers which may have values that are invalid according to JMS specification. For example some message systems such as WMQ do this with header names using prefix JMS_IBM_MQMD_ containing values with byte array or other invalid types. You can specify multiple header names separated by comma, and use as suffix for wildcard matching. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"required": false,
@ -1315,7 +1316,7 @@
},
"allowNullBody": {
"displayName": "Allow Null Body",
"description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown.",
"description": "Whether to allow sending messages with no body. If this option is false and the message body is null, then an JMSException is thrown. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1344,7 +1345,7 @@
},
"alwaysCopyMessage": {
"displayName": "Always Copy Message",
"description": "If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set)",
"description": "If true, Camel will always make a JMS message copy of the message when it is passed to the producer for sending. Copying the message is needed in some situations, such as when a replyToDestinationSelectorName is set (incidentally, Camel will set the alwaysCopyMessage option to true, if a replyToDestinationSelectorName is set). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1373,7 +1374,7 @@
},
"correlationProperty": {
"displayName": "Correlation Property",
"description": "When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel.",
"description": "When using InOut exchange pattern use this JMS property instead of JMSCorrelationID JMS property to correlate messages. If set messages will be correlated solely on the value of this property JMSCorrelationID property will be ignored and not set by Camel. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"required": false,
@ -1401,7 +1402,7 @@
},
"disableTimeToLive": {
"displayName": "Disable Time To Live",
"description": "Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive\u003dtrue to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details.",
"description": "Use this option to force disabling time to live. For example when you do request/reply over JMS, then Camel will by default use the requestTimeout value as time to live on the message being sent. The problem is that the sender and receiver systems have to have their clocks synchronized, so they are in sync. This is not always so easy to archive. So you can use disableTimeToLive\u003dtrue to not set a time to live value on the sent message. Then the message will not expire on the receiver system. See below in section About time to live for more details. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1430,7 +1431,7 @@
},
"forceSendOriginalMessage": {
"displayName": "Force Send Original Message",
"description": "When using mapJmsMessage\u003dfalse Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received.",
"description": "When using mapJmsMessage\u003dfalse Camel will create a new JMS message to send to a new JMS destination if you touch the headers (get or set) during the route. Set this option to true to force Camel to send the original JMS message that was received. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1459,7 +1460,7 @@
},
"includeSentJMSMessageID": {
"displayName": "Include Sent JMSMessage ID",
"description": "Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination.",
"description": "Only applicable when sending to JMS destination using InOnly (eg fire and forget). Enabling this option will enrich the Camel Exchange with the actual JMSMessageID that was used by the JMS client when the message was sent to the JMS destination. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1488,7 +1489,7 @@
},
"replyToCacheLevelName": {
"displayName": "Reply To Cache Level Name",
"description": "Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName\u003dCACHE_NONE to work. Note: If using temporary queues then CACHE_NONE is not allowed, and you must use a higher value such as CACHE_CONSUMER or CACHE_SESSION.",
"description": "Sets the cache level by name for the reply consumer when doing request/reply over JMS. This option only applies when using fixed reply queues (not temporary). Camel will by default use: CACHE_CONSUMER for exclusive or shared w/ replyToSelectorName. And CACHE_SESSION for shared without replyToSelectorName. Some JMS brokers such as IBM WebSphere may require to set the replyToCacheLevelName\u003dCACHE_NONE to work. Note: If using temporary queues then CACHE_NONE is not allowed, and you must use a higher value such as CACHE_CONSUMER or CACHE_SESSION. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"required": false,
@ -1526,7 +1527,7 @@
},
"replyToDestinationSelectorName": {
"displayName": "Reply To Destination Selector Name",
"description": "Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue).",
"description": "Sets the JMS Selector using the fixed name to be used so you can filter out your own replies from the others when using a shared queue (that is, if you are not using a temporary reply queue). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"required": false,
@ -1554,7 +1555,7 @@
},
"streamMessageTypeEnabled": {
"displayName": "Stream Message Type Enabled",
"description": "Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data.",
"description": "Sets whether StreamMessage type is enabled or not. Message payloads of streaming kind such as files, InputStream, etc will either by sent as BytesMessage or StreamMessage. This option controls which kind will be used. By default BytesMessage is used which enforces the entire message payload to be read into memory. By enabling this option the message payload is read into memory in chunks and each chunk is then written to the StreamMessage until no more data. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"required": false,
@ -1583,7 +1584,7 @@
},
"allowAutoWiredConnectionFactory": {
"displayName": "Allow Auto Wired Connection Factory",
"description": "Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default.",
"description": "Whether to auto-discover ConnectionFactory from the registry, if no connection factory has been configured. If only one instance of ConnectionFactory is found then it will be used. This is enabled by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "property",
@ -1599,7 +1600,7 @@
},
"allowAutoWiredDestinationResolver": {
"displayName": "Allow Auto Wired Destination Resolver",
"description": "Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default.",
"description": "Whether to auto-discover DestinationResolver from the registry, if no destination resolver has been configured. If only one instance of DestinationResolver is found then it will be used. This is enabled by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "property",
@ -1615,7 +1616,7 @@
},
"allowSerializedHeaders": {
"displayName": "Allow Serialized Headers",
"description": "Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level.",
"description": "Controls whether or not to include serialized headers. Applies only when transferExchange is true. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1644,7 +1645,7 @@
},
"artemisStreamingEnabled": {
"displayName": "Artemis Streaming Enabled",
"description": "Whether optimizing for Apache Artemis streaming mode.",
"description": "Whether optimizing for Apache Artemis streaming mode. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1673,7 +1674,7 @@
},
"asyncStartListener": {
"displayName": "Async Start Listener",
"description": "Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry.",
"description": "Whether to startup the JmsConsumer message listener asynchronously, when starting a route. For example if a JmsConsumer cannot get a connection to a remote JMS broker, then it may block while retrying and/or failover. This will cause Camel to block while starting routes. By setting this option to true, you will let routes startup, while the JmsConsumer connects to the JMS broker using a dedicated thread in asynchronous mode. If this option is used, then beware that if the connection could not be established, then an exception is logged at WARN level, and the consumer will not be able to receive messages; You can then restart the route to retry. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1702,7 +1703,7 @@
},
"asyncStopListener": {
"displayName": "Async Stop Listener",
"description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route.",
"description": "Whether to stop the JmsConsumer message listener asynchronously, when stopping a route. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1731,7 +1732,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1756,7 +1757,7 @@
},
"configuration": {
"displayName": "Configuration",
"description": "To use a shared JMS configuration",
"description": "To use a shared JMS configuration. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "property",
@ -1771,7 +1772,7 @@
},
"destinationResolver": {
"displayName": "Destination Resolver",
"description": "A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry).",
"description": "A pluggable org.springframework.jms.support.destination.DestinationResolver that allows you to use your own resolver (for example, to lookup the real destination in a JNDI registry). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -1799,7 +1800,7 @@
},
"errorHandler": {
"displayName": "Error Handler",
"description": "Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler.",
"description": "Specifies a org.springframework.util.ErrorHandler to be invoked in case of any uncaught exceptions thrown while processing a Message. By default these exceptions will be logged at the WARN level, if no errorHandler has been configured. You can configure logging level and whether stack traces should be logged using errorHandlerLoggingLevel and errorHandlerLogStackTrace options. This makes it much easier to configure, than having to code a custom errorHandler. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -1827,7 +1828,7 @@
},
"exceptionListener": {
"displayName": "Exception Listener",
"description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions.",
"description": "Specifies the JMS Exception Listener that is to be notified of any underlying JMS exceptions. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -1855,7 +1856,7 @@
},
"idleConsumerLimit": {
"displayName": "Idle Consumer Limit",
"description": "Specify the limit for the number of consumers that are allowed to be idle at any given time.",
"description": "Specify the limit for the number of consumers that are allowed to be idle at any given time. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"required": false,
@ -1884,7 +1885,7 @@
},
"idleTaskExecutionLimit": {
"displayName": "Idle Task Execution Limit",
"description": "Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring.",
"description": "Specifies the limit for idle executions of a receive task, not having received any message within its execution. If this limit is reached, the task will shut down and leave receiving to other executing tasks (in the case of dynamic scheduling; see the maxConcurrentConsumers setting). There is additional doc available from Spring. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"required": false,
@ -1913,7 +1914,7 @@
},
"includeAllJMSXProperties": {
"displayName": "Include All JMSXProperties",
"description": "Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply.",
"description": "Whether to include all JMSXxxx properties when mapping from JMS to Camel Message. Setting this to true will include properties such as JMSXAppID, and JMSXUserID etc. Note: If you are using a custom headerFilterStrategy then this option does not apply. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -1942,7 +1943,7 @@
},
"jmsKeyFormatStrategy": {
"displayName": "Jms Key Format Strategy",
"description": "Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation.",
"description": "Pluggable strategy for encoding and decoding JMS keys so they can be compliant with the JMS specification. Camel provides two implementations out of the box: default and passthrough. The default strategy will safely marshal dots and hyphens (. and -). The passthrough strategy leaves the key as is. Can be used for JMS brokers which do not care whether JMS header keys contain illegal characters. You can provide your own implementation of the org.apache.camel.component.jms.JmsKeyFormatStrategy and refer to it using the # notation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -1977,7 +1978,7 @@
},
"mapJmsMessage": {
"displayName": "Map Jms Message",
"description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc.",
"description": "Specifies whether Camel should auto map the received JMS message to a suited payload type, such as javax.jms.TextMessage to a String etc. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2006,7 +2007,7 @@
},
"maxMessagesPerTask": {
"displayName": "Max Messages Per Task",
"description": "The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required.",
"description": "The number of messages per task. -1 is unlimited. If you use a range for concurrent consumers (eg min max), then this option can be used to set a value to eg 100 to control how fast the consumers will shrink when less work is required. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"required": false,
@ -2035,7 +2036,7 @@
},
"messageConverter": {
"displayName": "Message Converter",
"description": "To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message.",
"description": "To use a custom Spring org.springframework.jms.support.converter.MessageConverter so you can be in control how to map to/from a javax.jms.Message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -2063,7 +2064,7 @@
},
"messageCreatedStrategy": {
"displayName": "Message Created Strategy",
"description": "To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message.",
"description": "To use the given MessageCreatedStrategy which are invoked when Camel creates new instances of javax.jms.Message objects when Camel is sending a JMS message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -2091,7 +2092,7 @@
},
"messageIdEnabled": {
"displayName": "Message Id Enabled",
"description": "When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value.",
"description": "When sending, specifies whether message IDs should be added. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the message ID set to null; if the provider ignores the hint, the message ID must be set to its normal unique value. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2120,7 +2121,7 @@
},
"messageListenerContainerFactory": {
"displayName": "Message Listener Container Factory",
"description": "Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom.",
"description": "Registry ID of the MessageListenerContainerFactory used to determine what org.springframework.jms.listener.AbstractMessageListenerContainer to use to consume messages. Setting this will automatically set consumerType to Custom. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -2148,7 +2149,7 @@
},
"messageTimestampEnabled": {
"displayName": "Message Timestamp Enabled",
"description": "Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value.",
"description": "Specifies whether timestamps should be enabled by default on sending messages. This is just an hint to the JMS broker. If the JMS provider accepts this hint, these messages must have the timestamp set to zero; if the provider ignores the hint the timestamp must be set to its normal value. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2177,7 +2178,7 @@
},
"pubSubNoLocal": {
"displayName": "Pub Sub No Local",
"description": "Specifies whether to inhibit the delivery of messages published by its own connection.",
"description": "Specifies whether to inhibit the delivery of messages published by its own connection. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2206,7 +2207,7 @@
},
"queueBrowseStrategy": {
"displayName": "Queue Browse Strategy",
"description": "To use a custom QueueBrowseStrategy when browsing queues",
"description": "To use a custom QueueBrowseStrategy when browsing queues. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "property",
@ -2221,7 +2222,7 @@
},
"receiveTimeout": {
"displayName": "Receive Timeout",
"description": "The timeout for receiving messages (in milliseconds).",
"description": "The timeout for receiving messages (in milliseconds). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"required": false,
@ -2250,7 +2251,7 @@
},
"recoveryInterval": {
"displayName": "Recovery Interval",
"description": "Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds.",
"description": "Specifies the interval between recovery attempts, i.e. when a connection is being refreshed, in milliseconds. The default is 5000 ms, that is, 5 seconds. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"required": false,
@ -2279,7 +2280,7 @@
},
"requestTimeoutCheckerInterval": {
"displayName": "Request Timeout Checker Interval",
"description": "Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout.",
"description": "Configures how often Camel should check for timed out Exchanges when doing request/reply over JMS. By default Camel checks once per second. But if you must react faster when a timeout occurs, then you can lower this interval, to check more frequently. The timeout is determined by the option requestTimeout. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"required": false,
@ -2308,7 +2309,7 @@
},
"transferException": {
"displayName": "Transfer Exception",
"description": "If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer!",
"description": "If enabled and you are using Request Reply messaging (InOut) and an Exchange failed on the consumer side, then the caused Exception will be send back in response as a javax.jms.ObjectMessage. If the client is Camel, the returned Exception is rethrown. This allows you to use Camel JMS as a bridge in your routing - for example, using persistent queues to enable robust routing. Notice that if you also have transferExchange enabled, this option takes precedence. The caught exception is required to be serializable. The original Exception on the consumer side can be wrapped in an outer exception such as org.apache.camel.RuntimeCamelException when returned to the producer. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer! For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2337,7 +2338,7 @@
},
"transferExchange": {
"displayName": "Transfer Exchange",
"description": "You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer having to use compatible Camel versions!",
"description": "You can transfer the exchange over the wire instead of just the body and headers. The following fields are transferred: In body, Out body, Fault body, In headers, Out headers, Fault headers, exchange properties, exchange exception. This requires that the objects are serializable. Camel will exclude any non-serializable objects and log it at WARN level. You must enable this option on both the producer and consumer side, so Camel knows the payloads is an Exchange and not a regular payload. Use this with caution as the data is using Java Object serialization and requires the received to be able to deserialize the data at Class level, which forces a strong coupling between the producers and consumer having to use compatible Camel versions! For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2366,7 +2367,7 @@
},
"useMessageIDAsCorrelationID": {
"displayName": "Use Message IDAs Correlation ID",
"description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages.",
"description": "Specifies whether JMSMessageID should always be used as JMSCorrelationID for InOut messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -2395,7 +2396,7 @@
},
"waitForProvisionCorrelationToBeUpdatedCounter": {
"displayName": "Wait For Provision Correlation To Be Updated Counter",
"description": "Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled.",
"description": "Number of times to wait for provisional correlation id to be updated to the actual correlation id when doing request/reply over JMS and when the option useMessageIDAsCorrelationID is enabled. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"required": false,
@ -2424,7 +2425,7 @@
},
"waitForProvisionCorrelationToBeUpdatedThreadSleepingTime": {
"displayName": "Wait For Provision Correlation To Be Updated Thread Sleeping Time",
"description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated.",
"description": "Interval in millis to sleep each time while waiting for provisional correlation id to be updated. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"required": false,
@ -2453,7 +2454,7 @@
},
"headerFilterStrategy": {
"displayName": "Header Filter Strategy",
"description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message.",
"description": "To use a custom org.apache.camel.spi.HeaderFilterStrategy to filter header to and from Camel message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "filter",
"type": "object",
"required": false,
@ -2477,7 +2478,7 @@
},
"errorHandlerLoggingLevel": {
"displayName": "Error Handler Logging Level",
"description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions.",
"description": "Allows to configure the default errorHandler logging level for logging uncaught exceptions. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,logging",
"type": "object",
"required": false,
@ -2517,7 +2518,7 @@
},
"errorHandlerLogStackTrace": {
"displayName": "Error Handler Log Stack Trace",
"description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler.",
"description": "Allows to control whether stacktraces should be logged or not, by the default errorHandler. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,logging",
"type": "boolean",
"required": false,
@ -2546,9 +2547,9 @@
},
"password": {
"displayName": "Password",
"description": "Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.",
"description": "Password to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"type": "password",
"required": false,
"hidden": true,
"group": "security",
@ -2574,7 +2575,7 @@
},
"username": {
"displayName": "Username",
"description": "Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory.",
"description": "Username to use with the ConnectionFactory. You can also configure username/password directly on the ConnectionFactory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"required": false,
@ -2602,7 +2603,7 @@
},
"transacted": {
"displayName": "Transacted",
"description": "Specifies whether to use transacted mode",
"description": "Specifies whether to use transacted mode. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "transaction",
"type": "boolean",
"required": false,
@ -2631,7 +2632,7 @@
},
"lazyCreateTransactionManager": {
"displayName": "Lazy Create Transaction Manager",
"description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted\u003dtrue.",
"description": "If true, Camel will create a JmsTransactionManager, if there is no transactionManager injected when option transacted\u003dtrue. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "transaction,advanced",
"type": "boolean",
"required": false,
@ -2660,7 +2661,7 @@
},
"transactionManager": {
"displayName": "Transaction Manager",
"description": "The Spring transaction manager to use.",
"description": "The Spring transaction manager to use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "transaction,advanced",
"type": "object",
"required": false,
@ -2688,7 +2689,7 @@
},
"transactionName": {
"displayName": "Transaction Name",
"description": "The name of the transaction to use.",
"description": "The name of the transaction to use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "transaction,advanced",
"type": "string",
"required": false,
@ -2716,7 +2717,7 @@
},
"transactionTimeout": {
"displayName": "Transaction Timeout",
"description": "The timeout value of the transaction (in seconds), if using transacted mode.",
"description": "The timeout value of the transaction (in seconds), if using transacted mode. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "transaction,advanced",
"type": "number",
"required": false,
@ -2745,7 +2746,7 @@
},
"destinationType": {
"displayName": "Destination Type",
"description": "The kind of destination to use",
"description": "The kind of destination to use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -2786,7 +2787,7 @@
},
"exceptionHandler": {
"displayName": "Exception Handler",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -2802,7 +2803,7 @@
},
"exchangePattern": {
"displayName": "Exchange Pattern",
"description": "Sets the exchange pattern when the consumer creates an exchange.",
"description": "Sets the exchange pattern when the consumer creates an exchange. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"kind": "parameter",
@ -2825,7 +2826,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -2838,6 +2839,30 @@
"javaType": "boolean",
"deprecated": false
}
},
"maxConnections": {
"type": "number",
"group": "common",
"description": "Maximum number of connection. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"required": true,
"displayName": "Max Connections",
"defaultValue": 10
},
"maxSessionsPerConnection": {
"type": "number",
"group": "common",
"description": "Maximum number of sessions for each connection. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"required": true,
"displayName": "Max Sessions Per Connection",
"defaultValue": 100
},
"connectionString": {
"type": "String",
"group": "common",
"required": true,
"displayName": "Connection string",
"description": "ConnectionFactory uri. Format: (protocol://host:port[,protocol://host:port]). Example: (tcp://192.168.0.11:61616,tcp://192.168.0.12:61616). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jms-component.html\">Camel docs</a>",
"defaultValue": "(tcp://localhost:61616)"
}
},
"##camel": {
@ -5970,22 +5995,9 @@
"outputs": {
"init": {
"fields": {
"password": {
"type": "String",
"group": "entaxy"
},
"username": {
"type": "String",
"group": "entaxy"
},
"connectionString": {
"type": "String",
"group": "entaxy",
"required": true,
"displayName": "Connection string",
"description": "ConnectionFactory uri. Format: (protocol://host:port). Example: (tcp://localhost:61616)",
"defaultValue": "(tcp://localhost:61616)"
},
"maxConnections": {},
"maxSessionsPerConnection": {},
"connectionString": {},
"@IMPORT": [
{
"sourceFactoryId": "#",
@ -6003,6 +6015,15 @@
}
}
]
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeTypes":["string","password","number"],
"includeNames":["camel_username","camel_password","connectionString","maxConnections","maxSessionsPerConnection"],
"includePatterns":[]
}
}
},
"path": {

View File

@ -6,16 +6,17 @@
"isAbstract": false,
"camelOriginComponent": "file",
"label": "file,core",
"description": "Read and write files.",
"description": "The File component provides access to file systems, allowing files to be processed by any other Camel Components or messages from other components to be saved to disk. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"displayName": "FILE",
"camelOrigin": "camel-file",
"camelOriginJavaType": "org.apache.camel.component.file.FileComponent",
"category": "adapter"
"category0": "adapter"
},
"entaxy.runtime.connection": {},
"fields": {
"bridgeErrorHandler": {
"displayName": "Bridge Error Handler",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -40,7 +41,7 @@
},
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -65,7 +66,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -90,7 +91,7 @@
},
"directoryName": {
"displayName": "Directory Name",
"description": "The starting directory",
"description": "The starting directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -106,7 +107,7 @@
},
"charset": {
"displayName": "Charset",
"description": "This option is used to specify the encoding of the file. You can use this on the consumer, to specify the encodings of the files, which allow Camel to know the charset it should load the file content in case the file content is being accessed. Likewise when writing a file, you can use this option to specify which charset to write the file as well. Do mind that when writing the file Camel may have to read the message content into memory to be able to convert the data into the configured charset, so do not use this if you have big messages.",
"description": "This option is used to specify the encoding of the file. You can use this on the consumer, to specify the encodings of the files, which allow Camel to know the charset it should load the file content in case the file content is being accessed. Likewise when writing a file, you can use this option to specify which charset to write the file as well. Do mind that when writing the file Camel may have to read the message content into memory to be able to convert the data into the configured charset, so do not use this if you have big messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -121,7 +122,7 @@
},
"doneFileName": {
"displayName": "Done File Name",
"description": "Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders.The done file is always expected in the same folder as the original file. Only ${file.name} and ${file.name.next} is supported as dynamic placeholders.",
"description": "Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders.The done file is always expected in the same folder as the original file. Only ${file.name} and ${file.name.next} is supported as dynamic placeholders. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -136,7 +137,7 @@
},
"fileName": {
"displayName": "File Name",
"description": "Use Expression such as File Language to dynamically set the filename. For consumers, it\u0027s used as a filename filter. For producers, it\u0027s used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today\u0027s file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt. The producers support the CamelOverruleFileName header which takes precedence over any existing CamelFileName header; the CamelOverruleFileName is a header that is used only once, and makes it easier as this avoids to temporary store CamelFileName and have to restore it afterwards.",
"description": "Use Expression such as File Language to dynamically set the filename. For consumers, it\u0027s used as a filename filter. For producers, it\u0027s used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today\u0027s file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt. The producers support the CamelOverruleFileName header which takes precedence over any existing CamelFileName header; the CamelOverruleFileName is a header that is used only once, and makes it easier as this avoids to temporary store CamelFileName and have to restore it afterwards. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -151,7 +152,7 @@
},
"delete": {
"displayName": "Delete",
"description": "If true, the file will be deleted after it is processed successfully.",
"description": "If true, the file will be deleted after it is processed successfully. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -167,7 +168,7 @@
},
"moveFailed": {
"displayName": "Move Failed",
"description": "Sets the move failure expression based on Simple language. For example, to move files into a .error subdirectory use: .error. Note: When moving the files to the fail location Camel will handle the error and will not pick up the file again.",
"description": "Sets the move failure expression based on Simple language. For example, to move files into a .error subdirectory use: .error. Note: When moving the files to the fail location Camel will handle the error and will not pick up the file again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"kind": "parameter",
@ -182,7 +183,7 @@
},
"noop": {
"displayName": "Noop",
"description": "If true, the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop\u003dtrue, Camel will set idempotent\u003dtrue as well, to avoid consuming the same files over and over again.",
"description": "If true, the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop\u003dtrue, Camel will set idempotent\u003dtrue as well, to avoid consuming the same files over and over again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -198,7 +199,7 @@
},
"preMove": {
"displayName": "Pre Move",
"description": "Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order.",
"description": "Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"kind": "parameter",
@ -213,7 +214,7 @@
},
"preSort": {
"displayName": "Pre Sort",
"description": "When pre-sort is enabled then the consumer will sort the file and directory names during polling, that was retrieved from the file system. You may want to do this in case you need to operate on the files in a sorted order. The pre-sort is executed before the consumer starts to filter, and accept files to process by Camel. This option is default\u003dfalse meaning disabled.",
"description": "When pre-sort is enabled then the consumer will sort the file and directory names during polling, that was retrieved from the file system. You may want to do this in case you need to operate on the files in a sorted order. The pre-sort is executed before the consumer starts to filter, and accept files to process by Camel. This option is default\u003dfalse meaning disabled. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -229,7 +230,7 @@
},
"recursive": {
"displayName": "Recursive",
"description": "If a directory, will look for files in all the sub-directories as well.",
"description": "If a directory, will look for files in all the sub-directories as well. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -245,7 +246,7 @@
},
"sendEmptyMessageWhenIdle": {
"displayName": "Send Empty Message When Idle",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -261,7 +262,7 @@
},
"directoryMustExist": {
"displayName": "Directory Must Exist",
"description": "Similar to the startingDirectoryMustExist option but this applies during polling (after starting the consumer).",
"description": "Similar to the startingDirectoryMustExist option but this applies during polling (after starting the consumer). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -277,7 +278,7 @@
},
"exceptionHandler": {
"displayName": "Exception Handler",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -293,7 +294,7 @@
},
"exchangePattern": {
"displayName": "Exchange Pattern",
"description": "Sets the exchange pattern when the consumer creates an exchange.",
"description": "Sets the exchange pattern when the consumer creates an exchange. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "String",
"kind": "parameter",
@ -316,7 +317,7 @@
},
"extendedAttributes": {
"displayName": "Extended Attributes",
"description": "To define which file attributes of interest. Like posix:permissions,posix:owner,basic:lastAccessTime, it supports basic wildcard like posix:, basic:lastAccessTime",
"description": "To define which file attributes of interest. Like posix:permissions,posix:owner,basic:lastAccessTime, it supports basic wildcard like posix:, basic:lastAccessTime. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"kind": "parameter",
@ -331,7 +332,7 @@
},
"inProgressRepository": {
"displayName": "In Progress Repository",
"description": "A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used.",
"description": "A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -346,7 +347,7 @@
},
"localWorkDirectory": {
"displayName": "Local Work Directory",
"description": "When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory.",
"description": "When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"kind": "parameter",
@ -361,7 +362,7 @@
},
"onCompletionExceptionHandler": {
"displayName": "On Completion Exception Handler",
"description": "To use a custom org.apache.camel.spi.ExceptionHandler to handle any thrown exceptions that happens during the file on completion process where the consumer does either a commit or rollback. The default implementation will log any exception at WARN level and ignore.",
"description": "To use a custom org.apache.camel.spi.ExceptionHandler to handle any thrown exceptions that happens during the file on completion process where the consumer does either a commit or rollback. The default implementation will log any exception at WARN level and ignore. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -376,7 +377,7 @@
},
"pollStrategy": {
"displayName": "Poll Strategy",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -391,7 +392,7 @@
},
"probeContentType": {
"displayName": "Probe Content Type",
"description": "Whether to enable probing of the content type. If enable then the consumer uses Files#probeContentType(java.nio.file.Path) to determine the content-type of the file, and store that as a header with key Exchange#FILE_CONTENT_TYPE on the Message.",
"description": "Whether to enable probing of the content type. If enable then the consumer uses Files#probeContentType(java.nio.file.Path) to determine the content-type of the file, and store that as a header with key Exchange#FILE_CONTENT_TYPE on the Message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -407,7 +408,7 @@
},
"processStrategy": {
"displayName": "Process Strategy",
"description": "A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply.",
"description": "A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -422,7 +423,7 @@
},
"startingDirectoryMustExist": {
"displayName": "Starting Directory Must Exist",
"description": "Whether the starting directory must exist. Mind that the autoCreate option is default enabled, which means the starting directory is normally auto created if it doesn\u0027t exist. You can disable autoCreate and enable this to ensure the starting directory must exist. Will thrown an exception if the directory doesn\u0027t exist.",
"description": "Whether the starting directory must exist. Mind that the autoCreate option is default enabled, which means the starting directory is normally auto created if it doesn\u0027t exist. You can disable autoCreate and enable this to ensure the starting directory must exist. Will thrown an exception if the directory doesn\u0027t exist. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -438,7 +439,7 @@
},
"startingDirectoryMustHaveAccess": {
"displayName": "Starting Directory Must Have Access",
"description": "Whether the starting directory has access permissions. Mind that the startingDirectoryMustExist parameter must be set to true in order to verify that the directory exists. Will thrown an exception if the directory doesn\u0027t have read and write permissions.",
"description": "Whether the starting directory has access permissions. Mind that the startingDirectoryMustExist parameter must be set to true in order to verify that the directory exists. Will thrown an exception if the directory doesn\u0027t have read and write permissions. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -454,7 +455,7 @@
},
"appendChars": {
"displayName": "Append Chars",
"description": "Used to append characters (text) after writing files. This can for example be used to add new lines or other separators when writing and appending to existing files. To specify new-line (slash-n or slash-r) or tab (slash-t) characters then escape with an extra slash, eg slash-slash-n.",
"description": "Used to append characters (text) after writing files. This can for example be used to add new lines or other separators when writing and appending to existing files. To specify new-line (slash-n or slash-r) or tab (slash-t) characters then escape with an extra slash, eg slash-slash-n. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -469,7 +470,7 @@
},
"fileExist": {
"displayName": "File Exist",
"description": "What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. The option eagerDeleteTargetFile can be used to control what to do if an moving the file, and there exists already an existing file, otherwise causing the move operation to fail. The Move option will move any existing files, before writing the target file. - TryRename is only applicable if tempFileName option is in use. This allows to try renaming the file from the temporary name to the actual name, without doing any exists check. This check may be faster on some file systems and especially FTP servers.",
"description": "What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. The option eagerDeleteTargetFile can be used to control what to do if an moving the file, and there exists already an existing file, otherwise causing the move operation to fail. The Move option will move any existing files, before writing the target file. - TryRename is only applicable if tempFileName option is in use. This allows to try renaming the file from the temporary name to the actual name, without doing any exists check. This check may be faster on some file systems and especially FTP servers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "String",
"kind": "parameter",
@ -496,7 +497,7 @@
},
"flatten": {
"displayName": "Flatten",
"description": "Flatten is used to flatten the file name path to strip any leading paths, so it\u0027s just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths.",
"description": "Flatten is used to flatten the file name path to strip any leading paths, so it\u0027s just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"kind": "parameter",
@ -512,7 +513,7 @@
},
"jailStartingDirectory": {
"displayName": "Jail Starting Directory",
"description": "Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders.",
"description": "Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"kind": "parameter",
@ -528,7 +529,7 @@
},
"moveExisting": {
"displayName": "Move Existing",
"description": "Expression (such as File Language) used to compute file name to use when fileExist\u003dMove is configured. To move files into a backup subdirectory just enter backup. This option only supports the following File Language tokens: file:name, file:name.ext, file:name.noext, file:onlyname, file:onlyname.noext, file:ext, and file:parent. Notice the file:parent is not supported by the FTP component, as the FTP component can only move any existing files to a relative directory based on current dir as base.",
"description": "Expression (such as File Language) used to compute file name to use when fileExist\u003dMove is configured. To move files into a backup subdirectory just enter backup. This option only supports the following File Language tokens: file:name, file:name.ext, file:name.noext, file:onlyname, file:onlyname.noext, file:ext, and file:parent. Notice the file:parent is not supported by the FTP component, as the FTP component can only move any existing files to a relative directory based on current dir as base. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -543,7 +544,7 @@
},
"tempFileName": {
"displayName": "Temp File Name",
"description": "The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option \u0027fileName\u0027, not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir.",
"description": "The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option \u0027fileName\u0027, not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -558,7 +559,7 @@
},
"tempPrefix": {
"displayName": "Temp Prefix",
"description": "This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files.",
"description": "This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -573,7 +574,7 @@
},
"allowNullBody": {
"displayName": "Allow Null Body",
"description": "Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of \u0027Cannot write null body to file.\u0027 will be thrown. If the fileExist option is set to \u0027Override\u0027, then the file will be truncated, and if set to append the file will remain unchanged.",
"description": "Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of \u0027Cannot write null body to file.\u0027 will be thrown. If the fileExist option is set to \u0027Override\u0027, then the file will be truncated, and if set to append the file will remain unchanged. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -589,7 +590,7 @@
},
"chmod": {
"displayName": "Chmod",
"description": "Specify the file permissions which is sent by the producer, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it.",
"description": "Specify the file permissions which is sent by the producer, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"kind": "parameter",
@ -604,7 +605,7 @@
},
"chmodDirectory": {
"displayName": "Chmod Directory",
"description": "Specify the directory permissions used when the producer creates missing directories, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it.",
"description": "Specify the directory permissions used when the producer creates missing directories, the chmod value must be between 000 and 777; If there is a leading digit like in 0755 we will ignore it. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"kind": "parameter",
@ -619,7 +620,7 @@
},
"eagerDeleteTargetFile": {
"displayName": "Eager Delete Target File",
"description": "Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists\u003dOverride and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename. This option is also used to control whether to delete any existing files when fileExist\u003dMove is enabled, and an existing file exists. If this option copyAndDeleteOnRenameFails false, then an exception will be thrown if an existing file existed, if its true, then the existing file is deleted before the move operation.",
"description": "Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists\u003dOverride and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename. This option is also used to control whether to delete any existing files when fileExist\u003dMove is enabled, and an existing file exists. If this option copyAndDeleteOnRenameFails false, then an exception will be thrown if an existing file existed, if its true, then the existing file is deleted before the move operation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -635,7 +636,7 @@
},
"forceWrites": {
"displayName": "Force Writes",
"description": "Whether to force syncing writes to the file system. You can turn this off if you do not want this level of guarantee, for example if writing to logs / audit logs etc; this would yield better performance.",
"description": "Whether to force syncing writes to the file system. You can turn this off if you do not want this level of guarantee, for example if writing to logs / audit logs etc; this would yield better performance. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -651,7 +652,7 @@
},
"keepLastModified": {
"displayName": "Keep Last Modified",
"description": "Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers.",
"description": "Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -667,7 +668,7 @@
},
"moveExistingFileStrategy": {
"displayName": "Move Existing File Strategy",
"description": "Strategy (Custom Strategy) used to move file with special naming token to use when fileExist\u003dMove is configured. By default, there is an implementation used if no custom strategy is provided",
"description": "Strategy (Custom Strategy) used to move file with special naming token to use when fileExist\u003dMove is configured. By default, there is an implementation used if no custom strategy is provided. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "object",
"kind": "parameter",
@ -682,7 +683,7 @@
},
"autoCreate": {
"displayName": "Auto Create",
"description": "Automatically create missing directories in the file\u0027s pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to.",
"description": "Automatically create missing directories in the file\u0027s pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -698,7 +699,7 @@
},
"bufferSize": {
"displayName": "Buffer Size",
"description": "Buffer size in bytes used for writing files (or in case of FTP for downloading and uploading files).",
"description": "Buffer size in bytes used for writing files (or in case of FTP for downloading and uploading files). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -714,7 +715,7 @@
},
"copyAndDeleteOnRenameFail": {
"displayName": "Copy And Delete On Rename Fail",
"description": "Whether to fallback and do a copy and delete file, in case the file could not be renamed directly. This option is not available for the FTP component.",
"description": "Whether to fallback and do a copy and delete file, in case the file could not be renamed directly. This option is not available for the FTP component. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -730,7 +731,7 @@
},
"renameUsingCopy": {
"displayName": "Rename Using Copy",
"description": "Perform rename operations using a copy and delete strategy. This is primarily used in environments where the regular rename operation is unreliable (e.g. across different file systems or networks). This option takes precedence over the copyAndDeleteOnRenameFail parameter that will automatically fall back to the copy and delete strategy, but only after additional delays.",
"description": "Perform rename operations using a copy and delete strategy. This is primarily used in environments where the regular rename operation is unreliable (e.g. across different file systems or networks). This option takes precedence over the copyAndDeleteOnRenameFail parameter that will automatically fall back to the copy and delete strategy, but only after additional delays. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -746,7 +747,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -762,7 +763,7 @@
},
"antExclude": {
"displayName": "Ant Exclude",
"description": "Ant style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence over antInclude. Multiple exclusions may be specified in comma-delimited format.",
"description": "Ant style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence over antInclude. Multiple exclusions may be specified in comma-delimited format. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -777,7 +778,7 @@
},
"antFilterCaseSensitive": {
"displayName": "Ant Filter Case Sensitive",
"description": "Sets case sensitive flag on ant filter.",
"description": "Sets case sensitive flag on ant filter. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -793,7 +794,7 @@
},
"antInclude": {
"displayName": "Ant Include",
"description": "Ant style filter inclusion. Multiple inclusions may be specified in comma-delimited format.",
"description": "Ant style filter inclusion. Multiple inclusions may be specified in comma-delimited format. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -808,7 +809,7 @@
},
"eagerMaxMessagesPerPoll": {
"displayName": "Eager Max Messages Per Poll",
"description": "Allows for controlling whether the limit from maxMessagesPerPoll is eager or not. If eager then the limit is during the scanning of files. Where as false would scan all files, and then perform sorting. Setting this option to false allows for sorting all files first, and then limit the poll. Mind that this requires a higher memory usage as all file details are in memory to perform the sorting.",
"description": "Allows for controlling whether the limit from maxMessagesPerPoll is eager or not. If eager then the limit is during the scanning of files. Where as false would scan all files, and then perform sorting. Setting this option to false allows for sorting all files first, and then limit the poll. Mind that this requires a higher memory usage as all file details are in memory to perform the sorting. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -824,7 +825,7 @@
},
"exclude": {
"displayName": "Exclude",
"description": "Is used to exclude files, if filename matches the regex pattern (matching is case in-senstive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris",
"description": "Is used to exclude files, if filename matches the regex pattern (matching is case in-senstive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -839,7 +840,7 @@
},
"filter": {
"displayName": "Filter",
"description": "Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method.",
"description": "Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "object",
"kind": "parameter",
@ -854,7 +855,7 @@
},
"filterDirectory": {
"displayName": "Filter Directory",
"description": "Filters the directory based on Simple language. For example to filter on current date, you can use a simple date pattern such as ${date:now:yyyMMdd}",
"description": "Filters the directory based on Simple language. For example to filter on current date, you can use a simple date pattern such as ${date:now:yyyMMdd}. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -869,7 +870,7 @@
},
"filterFile": {
"displayName": "Filter File",
"description": "Filters the file based on Simple language. For example to filter on file size, you can use ${file:size} 5000",
"description": "Filters the file based on Simple language. For example to filter on file size, you can use ${file:size} 5000. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -884,7 +885,7 @@
},
"idempotent": {
"displayName": "Idempotent",
"description": "Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop\u003dtrue then idempotent will be enabled as well to avoid consuming the same files over and over again.",
"description": "Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop\u003dtrue then idempotent will be enabled as well to avoid consuming the same files over and over again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -900,7 +901,7 @@
},
"idempotentKey": {
"displayName": "Idempotent Key",
"description": "To use a custom idempotent key. By default the absolute path of the file is used. You can use the File Language, for example to use the file name and file size, you can do: idempotentKey\u003d${file:name}-${file:size}",
"description": "To use a custom idempotent key. By default the absolute path of the file is used. You can use the File Language, for example to use the file name and file size, you can do: idempotentKey\u003d${file:name}-${file:size}. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -915,7 +916,7 @@
},
"idempotentRepository": {
"displayName": "Idempotent Repository",
"description": "A pluggable repository org.apache.camel.spi.IdempotentRepository which by default use MemoryMessageIdRepository if none is specified and idempotent is true.",
"description": "A pluggable repository org.apache.camel.spi.IdempotentRepository which by default use MemoryMessageIdRepository if none is specified and idempotent is true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "object",
"kind": "parameter",
@ -930,7 +931,7 @@
},
"include": {
"displayName": "Include",
"description": "Is used to include files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris",
"description": "Is used to include files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -945,7 +946,7 @@
},
"maxDepth": {
"displayName": "Max Depth",
"description": "The maximum depth to traverse when recursively processing a directory.",
"description": "The maximum depth to traverse when recursively processing a directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -961,7 +962,7 @@
},
"maxMessagesPerPoll": {
"displayName": "Max Messages Per Poll",
"description": "To define a maximum messages to gather per poll. By default no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. Notice: If this option is in use then the File and FTP components will limit before any sorting. For example if you have 100000 files and use maxMessagesPerPoll\u003d500, then only the first 500 files will be picked up, and then sorted. You can use the eagerMaxMessagesPerPoll option and set this to false to allow to scan all files first and then sort afterwards.",
"description": "To define a maximum messages to gather per poll. By default no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. Notice: If this option is in use then the File and FTP components will limit before any sorting. For example if you have 100000 files and use maxMessagesPerPoll\u003d500, then only the first 500 files will be picked up, and then sorted. You can use the eagerMaxMessagesPerPoll option and set this to false to allow to scan all files first and then sort afterwards. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -976,7 +977,7 @@
},
"minDepth": {
"displayName": "Min Depth",
"description": "The minimum depth to start processing when recursively processing a directory. Using minDepth\u003d1 means the base directory. Using minDepth\u003d2 means the first sub directory.",
"description": "The minimum depth to start processing when recursively processing a directory. Using minDepth\u003d1 means the base directory. Using minDepth\u003d2 means the first sub directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -991,7 +992,7 @@
},
"move": {
"displayName": "Move",
"description": "Expression (such as Simple Language) used to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done.",
"description": "Expression (such as Simple Language) used to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1006,7 +1007,7 @@
},
"exclusiveReadLockStrategy": {
"displayName": "Exclusive Read Lock Strategy",
"description": "Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation.",
"description": "Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "object",
"kind": "parameter",
@ -1021,7 +1022,7 @@
},
"readLock": {
"displayName": "Read Lock",
"description": "Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Camel will wait until the file lock is granted. This option provides the build in strategies: - none - No read lock is in use - markerFile - Camel creates a marker file (fileName.camelLock) and then holds a lock on it. This option is not available for the FTP component - changed - Changed is using file length/modification timestamp to detect whether the file is currently being copied or not. Will at least use 1 sec to determine this, so this option cannot consume files as fast as the others, but can be more reliable as the JDK IO API cannot always determine whether a file is currently being used by another process. The option readLockCheckInterval can be used to set the check frequency. - fileLock - is for using java.nio.channels.FileLock. This option is not avail for Windows OS and the FTP component. This approach should be avoided when accessing a remote file system via a mount/share unless that file system supports distributed file locks. - rename - rename is for using a try to rename the file as a test if we can get exclusive read-lock. - idempotent - (only for file component) idempotent is for using a idempotentRepository as the read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-changed - (only for file component) idempotent-changed is for using a idempotentRepository and changed as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-rename - (only for file component) idempotent-rename is for using a idempotentRepository and rename as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that.Notice: The various read locks is not all suited to work in clustered mode, where concurrent consumers on different nodes is competing for the same files on a shared file system. The markerFile using a close to atomic operation to create the empty marker file, but its not guaranteed to work in a cluster. The fileLock may work better but then the file system need to support distributed file locks, and so on. Using the idempotent read lock can support clustering if the idempotent repository supports clustering, such as Hazelcast Component or Infinispan.",
"description": "Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Camel will wait until the file lock is granted. This option provides the build in strategies: - none - No read lock is in use - markerFile - Camel creates a marker file (fileName.camelLock) and then holds a lock on it. This option is not available for the FTP component - changed - Changed is using file length/modification timestamp to detect whether the file is currently being copied or not. Will at least use 1 sec to determine this, so this option cannot consume files as fast as the others, but can be more reliable as the JDK IO API cannot always determine whether a file is currently being used by another process. The option readLockCheckInterval can be used to set the check frequency. - fileLock - is for using java.nio.channels.FileLock. This option is not avail for Windows OS and the FTP component. This approach should be avoided when accessing a remote file system via a mount/share unless that file system supports distributed file locks. - rename - rename is for using a try to rename the file as a test if we can get exclusive read-lock. - idempotent - (only for file component) idempotent is for using a idempotentRepository as the read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-changed - (only for file component) idempotent-changed is for using a idempotentRepository and changed as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-rename - (only for file component) idempotent-rename is for using a idempotentRepository and rename as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that.Notice: The various read locks is not all suited to work in clustered mode, where concurrent consumers on different nodes is competing for the same files on a shared file system. The markerFile using a close to atomic operation to create the empty marker file, but its not guaranteed to work in a cluster. The fileLock may work better but then the file system need to support distributed file locks, and so on. Using the idempotent read lock can support clustering if the idempotent repository supports clustering, such as Hazelcast Component or Infinispan. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "string",
"kind": "parameter",
@ -1050,7 +1051,7 @@
},
"readLockCheckInterval": {
"displayName": "Read Lock Check Interval",
"description": "Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file. Notice: For FTP the default readLockCheckInterval is 5000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit.",
"description": "Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file. Notice: For FTP the default readLockCheckInterval is 5000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1066,7 +1067,7 @@
},
"readLockDeleteOrphanLockFiles": {
"displayName": "Read Lock Delete Orphan Lock Files",
"description": "Whether or not read lock with marker files should upon startup delete any orphan read lock files, which may have been left on the file system, if Camel was not properly shutdown (such as a JVM crash). If turning this option to false then any orphaned lock file will cause Camel to not attempt to pickup that file, this could also be due another node is concurrently reading files from the same shared directory.",
"description": "Whether or not read lock with marker files should upon startup delete any orphan read lock files, which may have been left on the file system, if Camel was not properly shutdown (such as a JVM crash). If turning this option to false then any orphaned lock file will cause Camel to not attempt to pickup that file, this could also be due another node is concurrently reading files from the same shared directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1082,7 +1083,7 @@
},
"readLockIdempotentReleaseAsync": {
"displayName": "Read Lock Idempotent Release Async",
"description": "Whether the delayed release task should be synchronous or asynchronous. See more details at the readLockIdempotentReleaseDelay option.",
"description": "Whether the delayed release task should be synchronous or asynchronous. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1098,7 +1099,7 @@
},
"readLockIdempotentReleaseAsyncPoolSize": {
"displayName": "Read Lock Idempotent Release Async Pool Size",
"description": "The number of threads in the scheduled thread pool when using asynchronous release tasks. Using a default of 1 core threads should be sufficient in almost all use-cases, only set this to a higher value if either updating the idempotent repository is slow, or there are a lot of files to process. This option is not in-use if you use a shared thread pool by configuring the readLockIdempotentReleaseExecutorService option. See more details at the readLockIdempotentReleaseDelay option.",
"description": "The number of threads in the scheduled thread pool when using asynchronous release tasks. Using a default of 1 core threads should be sufficient in almost all use-cases, only set this to a higher value if either updating the idempotent repository is slow, or there are a lot of files to process. This option is not in-use if you use a shared thread pool by configuring the readLockIdempotentReleaseExecutorService option. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1113,7 +1114,7 @@
},
"readLockIdempotentReleaseDelay": {
"displayName": "Read Lock Idempotent Release Delay",
"description": "Whether to delay the release task for a period of millis. This can be used to delay the release tasks to expand the window when a file is regarded as read-locked, in an active/active cluster scenario with a shared idempotent repository, to ensure other nodes cannot potentially scan and acquire the same file, due to race-conditions. By expanding the time-window of the release tasks helps prevents these situations. Note delaying is only needed if you have configured readLockRemoveOnCommit to true.",
"description": "Whether to delay the release task for a period of millis. This can be used to delay the release tasks to expand the window when a file is regarded as read-locked, in an active/active cluster scenario with a shared idempotent repository, to ensure other nodes cannot potentially scan and acquire the same file, due to race-conditions. By expanding the time-window of the release tasks helps prevents these situations. Note delaying is only needed if you have configured readLockRemoveOnCommit to true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1128,7 +1129,7 @@
},
"readLockIdempotentReleaseExecutorService": {
"displayName": "Read Lock Idempotent Release Executor Service",
"description": "To use a custom and shared thread pool for asynchronous release tasks. See more details at the readLockIdempotentReleaseDelay option.",
"description": "To use a custom and shared thread pool for asynchronous release tasks. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "object",
"kind": "parameter",
@ -1143,7 +1144,7 @@
},
"readLockLoggingLevel": {
"displayName": "Read Lock Logging Level",
"description": "Logging level used when a read lock could not be acquired. By default a DEBUG is logged. You can change this level, for example to OFF to not have any logging. This option is only applicable for readLock of types: changed, fileLock, idempotent, idempotent-changed, idempotent-rename, rename.",
"description": "Logging level used when a read lock could not be acquired. By default a DEBUG is logged. You can change this level, for example to OFF to not have any logging. This option is only applicable for readLock of types: changed, fileLock, idempotent, idempotent-changed, idempotent-rename, rename. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "String",
"kind": "parameter",
@ -1170,7 +1171,7 @@
},
"readLockMarkerFile": {
"displayName": "Read Lock Marker File",
"description": "Whether to use marker file with the changed, rename, or exclusive read lock types. By default a marker file is used as well to guard against other processes picking up the same files. This behavior can be turned off by setting this option to false. For example if you do not want to write marker files to the file systems by the Camel application.",
"description": "Whether to use marker file with the changed, rename, or exclusive read lock types. By default a marker file is used as well to guard against other processes picking up the same files. This behavior can be turned off by setting this option to false. For example if you do not want to write marker files to the file systems by the Camel application. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1186,7 +1187,7 @@
},
"readLockMinAge": {
"displayName": "Read Lock Min Age",
"description": "This option is applied only for readLock\u003dchanged. It allows to specify a minimum age the file must be before attempting to acquire the read lock. For example use readLockMinAge\u003d300s to require the file is at last 5 minutes old. This can speedup the changed read lock as it will only attempt to acquire files which are at least that given age.",
"description": "This option is applied only for readLock\u003dchanged. It allows to specify a minimum age the file must be before attempting to acquire the read lock. For example use readLockMinAge\u003d300s to require the file is at last 5 minutes old. This can speedup the changed read lock as it will only attempt to acquire files which are at least that given age. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1202,7 +1203,7 @@
},
"readLockMinLength": {
"displayName": "Read Lock Min Length",
"description": "This option is applied only for readLock\u003dchanged. It allows you to configure a minimum file length. By default Camel expects the file to contain data, and thus the default value is 1. You can set this option to zero, to allow consuming zero-length files.",
"description": "This option is applied only for readLock\u003dchanged. It allows you to configure a minimum file length. By default Camel expects the file to contain data, and thus the default value is 1. You can set this option to zero, to allow consuming zero-length files. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1218,7 +1219,7 @@
},
"readLockRemoveOnCommit": {
"displayName": "Read Lock Remove On Commit",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file is succeeded and a commit happens. By default the file is not removed which ensures that any race-condition do not occur so another active node may attempt to grab the file. Instead the idempotent repository may support eviction strategies that you can configure to evict the file name entry after X minutes - this ensures no problems with race conditions. See more details at the readLockIdempotentReleaseDelay option.",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file is succeeded and a commit happens. By default the file is not removed which ensures that any race-condition do not occur so another active node may attempt to grab the file. Instead the idempotent repository may support eviction strategies that you can configure to evict the file name entry after X minutes - this ensures no problems with race conditions. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1234,7 +1235,7 @@
},
"readLockRemoveOnRollback": {
"displayName": "Read Lock Remove On Rollback",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file failed and a rollback happens. If this option is false, then the file name entry is confirmed (as if the file did a commit).",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file failed and a rollback happens. If this option is false, then the file name entry is confirmed (as if the file did a commit). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1250,7 +1251,7 @@
},
"readLockTimeout": {
"displayName": "Read Lock Timeout",
"description": "Optional timeout in millis for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Camel will skip the file. At next poll Camel, will try the file again, and this time maybe the read-lock could be granted. Use a value of 0 or lower to indicate forever. Currently fileLock, changed and rename support the timeout. Notice: For FTP the default readLockTimeout value is 20000 instead of 10000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit.",
"description": "Optional timeout in millis for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Camel will skip the file. At next poll Camel, will try the file again, and this time maybe the read-lock could be granted. Use a value of 0 or lower to indicate forever. Currently fileLock, changed and rename support the timeout. Notice: For FTP the default readLockTimeout value is 20000 instead of 10000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1266,7 +1267,7 @@
},
"backoffErrorThreshold": {
"displayName": "Backoff Error Threshold",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1281,7 +1282,7 @@
},
"backoffIdleThreshold": {
"displayName": "Backoff Idle Threshold",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1296,7 +1297,7 @@
},
"backoffMultiplier": {
"displayName": "Backoff Multiplier",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1311,7 +1312,7 @@
},
"delay": {
"displayName": "Delay",
"description": "Milliseconds before the next poll.",
"description": "Milliseconds before the next poll. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1327,7 +1328,7 @@
},
"greedy": {
"displayName": "Greedy",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1343,7 +1344,7 @@
},
"initialDelay": {
"displayName": "Initial Delay",
"description": "Milliseconds before the first poll starts.",
"description": "Milliseconds before the first poll starts. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1359,7 +1360,7 @@
},
"repeatCount": {
"displayName": "Repeat Count",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1402,7 +1403,7 @@
},
"scheduledExecutorService": {
"displayName": "Scheduled Executor Service",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1417,7 +1418,7 @@
},
"scheduler": {
"displayName": "Scheduler",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "string",
"kind": "parameter",
@ -1441,7 +1442,7 @@
},
"schedulerProperties": {
"displayName": "Scheduler Properties",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1458,7 +1459,7 @@
},
"startScheduler": {
"displayName": "Start Scheduler",
"description": "Whether the scheduler should be auto started.",
"description": "Whether the scheduler should be auto started. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1474,7 +1475,7 @@
},
"timeUnit": {
"displayName": "Time Unit",
"description": "Time unit for initialDelay and delay options.",
"description": "Time unit for initialDelay and delay options. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "String",
"kind": "parameter",
@ -1502,7 +1503,7 @@
},
"useFixedDelay": {
"displayName": "Use Fixed Delay",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1518,7 +1519,7 @@
},
"shuffle": {
"displayName": "Shuffle",
"description": "To shuffle the list of files (sort in random order)",
"description": "To shuffle the list of files (sort in random order). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "boolean",
"kind": "parameter",
@ -1534,7 +1535,7 @@
},
"sortBy": {
"displayName": "Sort By",
"description": "Built-in sort by using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date.",
"description": "Built-in sort by using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "string",
"kind": "parameter",
@ -1549,7 +1550,7 @@
},
"sorter": {
"displayName": "Sorter",
"description": "Pluggable sorter as a java.util.Comparator class.",
"description": "Pluggable sorter as a java.util.Comparator class. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "object",
"kind": "parameter",
@ -1564,11 +1565,15 @@
},
"rootDirectory": {
"type": "String",
"displayName": "Root directory",
"description": "Root directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"group": "entaxy",
"required": true
},
"createResourceProvider": {
"type": "Boolean",
"displayName": "Create resource provider",
"description": "A customizable component defining and managing resource types within the storage system. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/file-component.html\">Camel docs</a>",
"group": "entaxy",
"required": true,
"defaultValue": false
@ -3066,6 +3071,14 @@
],
"rootDirectory": {},
"createResourceProvider": {}
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeNames":["rootDirectory"],
"includePatterns":[]
}
}
},
"path": {
@ -3198,4 +3211,4 @@
}
}
}
}
}

View File

@ -6,23 +6,21 @@
"isAbstract": false,
"camelOriginComponent": "ftp",
"label": "ftp",
"description": "Upload and download files to/from FTP servers.",
"camelOrigin": "camel-ftp",
"description": "This component provides access to remote file systems over the FTP and SFTP protocols. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"displayName": "FTP",
"camelOriginJavaType": "org.apache.camel.component.file.remote.FtpComponent"
},
"entaxy.runtime.connection": {},
"fields": {
"transferLoggingIntervalSeconds": {
"displayName": "Transfer Logging Interval Seconds",
"description": "Configures the interval in seconds to use when logging the progress of upload and download operations that are in-flight. This is used for logging progress when operations takes longer time.",
"description": "Configures the interval in seconds to use when logging the progress of upload and download operations that are in-flight. This is used for logging progress when operations takes longer time. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "common",
"type": "number",
"kind": "parameter",
"required": false,
"hidden": false,
"defaultValue": {
"value": "5"
},
"defaultValue": 5,
"group": "common",
"##origin": "camel",
"##camelDiff": {
@ -32,7 +30,7 @@
},
"transferLoggingLevel": {
"displayName": "Transfer Logging Level",
"description": "Configure the logging level to use when logging the progress of upload and download operations.",
"description": "Configure the logging level to use when logging the progress of upload and download operations. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "common",
"type": "object",
"kind": "parameter",
@ -59,7 +57,7 @@
},
"transferLoggingVerbose": {
"displayName": "Transfer Logging Verbose",
"description": "Configures whether the perform verbose (fine grained) logging of the progress of upload and download operations.",
"description": "Configures whether the perform verbose (fine grained) logging of the progress of upload and download operations. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "common",
"type": "boolean",
"kind": "parameter",
@ -75,7 +73,7 @@
},
"resumeDownload": {
"displayName": "Resume Download",
"description": "Configures whether resume download is enabled. This must be supported by the FTP server (almost all FTP servers support it). In addition the options localWorkDirectory must be configured so downloaded files are stored in a local directory, and the option binary must be enabled, which is required to support resuming of downloads.",
"description": "Configures whether resume download is enabled. This must be supported by the FTP server (almost all FTP servers support it). In addition the options localWorkDirectory must be configured so downloaded files are stored in a local directory, and the option binary must be enabled, which is required to support resuming of downloads. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -91,7 +89,7 @@
},
"handleDirectoryParserAbsoluteResult": {
"displayName": "Handle Directory Parser Absolute Result",
"description": "Allows you to set how the consumer will handle subfolders and files in the path if the directory parser results in with absolute paths The reason for this is that some FTP servers may return file names with absolute paths, and if so then the FTP component needs to handle this by converting the returned path into a relative path.",
"description": "Allows you to set how the consumer will handle subfolders and files in the path if the directory parser results in with absolute paths The reason for this is that some FTP servers may return file names with absolute paths, and if so then the FTP component needs to handle this by converting the returned path into a relative path. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -109,7 +107,7 @@
},
"activePortRange": {
"displayName": "Active Port Range",
"description": "Set the client side port range in active mode. The syntax is: minPort-maxPort Both port numbers are inclusive, eg 10000-19999 to include all 1xxxx ports.",
"description": "Set the client side port range in active mode. The syntax is: minPort-maxPort Both port numbers are inclusive, eg 10000-19999 to include all 1xxxx ports. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"kind": "parameter",
@ -126,15 +124,13 @@
},
"bufferSize": {
"displayName": "Buffer Size",
"description": "Buffer size in bytes used for writing files (or in case of FTP for downloading and uploading files).",
"description": "Buffer size in bytes used for writing files (or in case of FTP for downloading and uploading files). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
"required": false,
"hidden": false,
"defaultValue": {
"value": "131072"
},
"defaultValue": 131072,
"group": "advanced",
"##origin": "camel",
"##camelDiff": {
@ -144,7 +140,7 @@
},
"ftpClient": {
"displayName": "Ftp Client",
"description": "To use a custom instance of FTPClient",
"description": "To use a custom instance of FTPClient For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -159,7 +155,7 @@
},
"ftpClientConfig": {
"displayName": "Ftp Client Config",
"description": "To use a custom instance of FTPClientConfig to configure the FTP client the endpoint should use.",
"description": "To use a custom instance of FTPClientConfig to configure the FTP client the endpoint should use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -174,7 +170,7 @@
},
"ftpClientConfigParameters": {
"displayName": "Ftp Client Config Parameters",
"description": "Used by FtpComponent to provide additional parameters for the FTPClientConfig",
"description": "Used by FtpComponent to provide additional parameters for the FTPClientConfig For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -191,7 +187,7 @@
},
"ftpClientParameters": {
"displayName": "Ftp Client Parameters",
"description": "Used by FtpComponent to provide additional parameters for the FTPClient",
"description": "Used by FtpComponent to provide additional parameters for the FTPClient For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -208,7 +204,7 @@
},
"maximumReconnectAttempts": {
"displayName": "Maximum Reconnect Attempts",
"description": "Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.",
"description": "Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -223,7 +219,7 @@
},
"reconnectDelay": {
"displayName": "Reconnect Delay",
"description": "Delay in millis Camel will wait before performing a reconnect attempt.",
"description": "Delay in millis Camel will wait before performing a reconnect attempt. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -238,7 +234,7 @@
},
"siteCommand": {
"displayName": "Site Command",
"description": "Sets optional site command(s) to be executed after successful login. Multiple site commands can be separated using a new line character.",
"description": "Sets optional site command(s) to be executed after successful login. Multiple site commands can be separated using a new line character. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"kind": "parameter",
@ -255,7 +251,7 @@
},
"account": {
"displayName": "Account",
"description": "Account to use for login",
"description": "Account to use for login For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -269,13 +265,6 @@
"configurationClass": "org.apache.camel.component.file.remote.FtpConfiguration",
"configurationField": "configuration"
}
},
"connectionString": {
"displayName": "Connection String",
"description": "Format: [username@]hostname[:port]/directoryname",
"type": "String",
"required": true,
"group": "entaxy"
}
},
"##camel": {
@ -2002,7 +1991,7 @@
"group": "security",
"label": "security",
"required": false,
"type": "string",
"type": "password",
"javaType": "java.lang.String",
"deprecated": false,
"secret": true,
@ -2067,7 +2056,11 @@
"outputs": {
"init": {
"fields": {
"connectionString": {},
"username": {},
"password": {},
"host": {},
"port": {},
"directoryName": {},
"@IMPORT": [
{
"sourceFactoryId": "#",
@ -2085,6 +2078,15 @@
}
}
]
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeTypes":["string","password","number"],
"includeNames":["username","password","host","port","directoryName"],
"includePatterns":[]
}
}
},
"path": {

View File

@ -6,7 +6,8 @@
"isAbstract": false,
"camelOriginComponent": "jdbc",
"label": "database,sql,jdbc",
"description": "Access databases through SQL and JDBC.",
"description": "The JDBC component enables you to access databases through JDBC, where SQL queries (SELECT) and operations (INSERT, UPDATE, etc) are sent in the message body. This component uses the standard JDBC API, unlike the SQL Component component, which uses spring-jdbc. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"displayName": "JDBC",
"camelOrigin": "camel-jdbc",
"camelOriginJavaType": "org.apache.camel.component.jdbc.JdbcComponent"
},
@ -14,7 +15,7 @@
"fields": {
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -39,7 +40,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -64,7 +65,7 @@
},
"dataSourceName": {
"displayName": "Data Source Name",
"description": "Name of DataSource to lookup in the Registry. If the name is dataSource or default, then Camel will attempt to lookup a default DataSource from the registry, meaning if there is a only one instance of DataSource found, then this DataSource will be used.",
"description": "Name of DataSource to lookup in the Registry. If the name is dataSource or default, then Camel will attempt to lookup a default DataSource from the registry, meaning if there is a only one instance of DataSource found, then this DataSource will be used. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -80,7 +81,7 @@
},
"allowNamedParameters": {
"displayName": "Allow Named Parameters",
"description": "Whether to allow using named parameters in the queries.",
"description": "Whether to allow using named parameters in the queries. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -96,7 +97,7 @@
},
"outputClass": {
"displayName": "Output Class",
"description": "Specify the full package and class name to use as conversion when outputType\u003dSelectOne or SelectList.",
"description": "Specify the full package and class name to use as conversion when outputType\u003dSelectOne or SelectList. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -111,7 +112,7 @@
},
"outputType": {
"displayName": "Output Type",
"description": "Determines the output the producer should use.",
"description": "Determines the output the producer should use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "object",
"kind": "parameter",
@ -135,7 +136,7 @@
},
"parameters": {
"displayName": "Parameters",
"description": "Optional parameters to the java.sql.Statement. For example to set maxRows, fetchSize etc.",
"description": "Optional parameters to the java.sql.Statement. For example to set maxRows, fetchSize etc. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "object",
"kind": "parameter",
@ -152,7 +153,7 @@
},
"readSize": {
"displayName": "Read Size",
"description": "The default maximum number of rows that can be read by a polling query. The default value is 0.",
"description": "The default maximum number of rows that can be read by a polling query. The default value is 0. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "number",
"kind": "parameter",
@ -167,7 +168,7 @@
},
"resetAutoCommit": {
"displayName": "Reset Auto Commit",
"description": "Camel will set the autoCommit on the JDBC connection to be false, commit the change after executed the statement and reset the autoCommit flag of the connection at the end, if the resetAutoCommit is true. If the JDBC connection doesn\u0027t support to reset the autoCommit flag, you can set the resetAutoCommit flag to be false, and Camel will not try to reset the autoCommit flag. When used with XA transactions you most likely need to set it to false so that the transaction manager is in charge of committing this tx.",
"description": "Camel will set the autoCommit on the JDBC connection to be false, commit the change after executed the statement and reset the autoCommit flag of the connection at the end, if the resetAutoCommit is true. If the JDBC connection doesn\u0027t support to reset the autoCommit flag, you can set the resetAutoCommit flag to be false, and Camel will not try to reset the autoCommit flag. When used with XA transactions you most likely need to set it to false so that the transaction manager is in charge of committing this tx. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -183,7 +184,7 @@
},
"transacted": {
"displayName": "Transacted",
"description": "Whether transactions are in use.",
"description": "Whether transactions are in use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -199,7 +200,7 @@
},
"useGetBytesForBlob": {
"displayName": "Use Get Bytes For Blob",
"description": "To read BLOB columns as bytes instead of string data. This may be needed for certain databases such as Oracle where you must read BLOB columns as bytes.",
"description": "To read BLOB columns as bytes instead of string data. This may be needed for certain databases such as Oracle where you must read BLOB columns as bytes. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -215,7 +216,7 @@
},
"useHeadersAsParameters": {
"displayName": "Use Headers As Parameters",
"description": "Set this option to true to use the prepareStatementStrategy with named parameters. This allows to define queries with named placeholders, and use headers with the dynamic values for the query placeholders.",
"description": "Set this option to true to use the prepareStatementStrategy with named parameters. This allows to define queries with named placeholders, and use headers with the dynamic values for the query placeholders. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -231,7 +232,7 @@
},
"useJDBC4ColumnNameAndLabelSemantics": {
"displayName": "Use JDBC4 Column Name And Label Semantics",
"description": "Sets whether to use JDBC 4 or JDBC 3.0 or older semantic when retrieving column name. JDBC 4.0 uses columnLabel to get the column name where as JDBC 3.0 uses both columnName or columnLabel. Unfortunately JDBC drivers behave differently so you can use this option to work out issues around your JDBC driver if you get problem using this component This option is default true.",
"description": "Sets whether to use JDBC 4 or JDBC 3.0 or older semantic when retrieving column name. JDBC 4.0 uses columnLabel to get the column name where as JDBC 3.0 uses both columnName or columnLabel. Unfortunately JDBC drivers behave differently so you can use this option to work out issues around your JDBC driver if you get problem using this component This option is default true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -247,7 +248,7 @@
},
"beanRowMapper": {
"displayName": "Bean Row Mapper",
"description": "To use a custom org.apache.camel.component.jdbc.BeanRowMapper when using outputClass. The default implementation will lower case the row names and skip underscores, and dashes. For example CUST_ID is mapped as custId.",
"description": "To use a custom org.apache.camel.component.jdbc.BeanRowMapper when using outputClass. The default implementation will lower case the row names and skip underscores, and dashes. For example CUST_ID is mapped as custId. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -262,7 +263,7 @@
},
"prepareStatementStrategy": {
"displayName": "Prepare Statement Strategy",
"description": "Allows the plugin to use a custom org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control preparation of the query and prepared statement.",
"description": "Allows the plugin to use a custom org.apache.camel.component.jdbc.JdbcPrepareStatementStrategy to control preparation of the query and prepared statement. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -277,7 +278,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -293,7 +294,7 @@
},
"dataSourceUrl": {
"displayName": "Database connection URL",
"description": "The connection URL to be passed to our JDBC driver to establish a connection. Examples: 'jdbc:h2:./testH2Database', 'jdbc:postgresql://localhost:5432/testDatabase?loglevel=2', 'jdbc:mysql://localhost:3306/testDatabase?user=root', 'jdbc:oracle:thin:@localhost:1521:my_sid', 'jdbc:sqlserver://localhost\\\\mssql_instance:1433;databaseName=testDatabase'",
"description": "The connection URL to be passed to our JDBC driver to establish a connection. Examples: 'jdbc:h2:./testH2Database', 'jdbc:postgresql://localhost:5432/testDatabase?loglevel=2', 'jdbc:mysql://localhost:3306/testDatabase?user=root', 'jdbc:oracle:thin:@localhost:1521:my_sid', 'jdbc:sqlserver://localhost\\\\mssql_instance:1433;databaseName=testDatabase' For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"type": "string",
"required": true,
"defaultValue": "jdbc:h2:./data/h2/cache",
@ -301,7 +302,7 @@
},
"dataSourceClass": {
"displayName": "Driver class name",
"description": "The fully qualified Java class name of the JDBC driver to be used. Examples: 'org.h2.Driver', 'org.postgresql.Driver', 'com.mysql.jdbc.Driver', 'oracle.jdbc.OracleDriver', 'com.microsoft.sqlserver.jdbc.SQLServerDriver'",
"description": "The fully qualified Java class name of the JDBC driver to be used. Examples: 'org.h2.Driver', 'org.postgresql.Driver', 'com.mysql.jdbc.Driver', 'oracle.jdbc.OracleDriver', 'com.microsoft.sqlserver.jdbc.SQLServerDriver' For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"type": "string",
"required": true,
"defaultValue": "org.h2.Driver",
@ -309,15 +310,15 @@
},
"dataSourceUsername": {
"displayName": "Database username",
"description": "The connection user name to be passed to our JDBC driver to establish a connection.",
"description": "The connection user name to be passed to our JDBC driver to establish a connection. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"type": "string",
"required": false,
"group": "entaxy"
},
"dataSourcePassword": {
"displayName": "Database password",
"description": "The connection password to be passed to our JDBC driver to establish a connection.",
"type": "string",
"description": "The connection password to be passed to our JDBC driver to establish a connection. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/jdbc-component.html\">Camel docs</a>",
"type": "password",
"required": false,
"group": "entaxy"
}
@ -802,6 +803,15 @@
}
}
]
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeTypes":["string","password"],
"includeNames":["dataSourceUrl","dataSourceClass","dataSourceUsername","dataSourcePassword"],
"includePatterns":[]
}
}
},
"path": {

View File

@ -6,7 +6,8 @@
"isAbstract": false,
"camelOriginComponent": "mongodb",
"label": "database,nosql,mongodb",
"description": "Perform operations on MongoDB documents and collections.",
"description": "MongoDB is a very popular NoSQL solution and the camel-mongodb component integrates Camel with MongoDB allowing you to interact with MongoDB collections both as a producer (performing operations on the collection) and as a consumer (consuming documents from a MongoDB collection). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"displayName": "MONGODB",
"camelOrigin": "camel-mongodb",
"camelOriginJavaType": "org.apache.camel.component.mongodb.MongoDbComponent"
},
@ -14,7 +15,7 @@
"fields": {
"bridgeErrorHandler": {
"displayName": "Bridge Error Handler",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -39,7 +40,7 @@
},
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -64,7 +65,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -89,7 +90,7 @@
},
"connectionBean": {
"displayName": "Connection Bean",
"description": "Sets the connection bean reference used to lookup a client for connecting to a database.",
"description": "Sets the connection bean reference used to lookup a client for connecting to a database. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -105,7 +106,7 @@
},
"collection": {
"displayName": "Collection",
"description": "Sets the name of the MongoDB collection to bind to this endpoint",
"description": "Sets the name of the MongoDB collection to bind to this endpoint For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -120,7 +121,7 @@
},
"collectionIndex": {
"displayName": "Collection Index",
"description": "Sets the collection index (JSON FORMAT : { field1 : order1, field2 : order2})",
"description": "Sets the collection index (JSON FORMAT : { field1 : order1, field2 : order2}) For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -135,7 +136,7 @@
},
"createCollection": {
"displayName": "Create Collection",
"description": "Create collection during initialisation if it doesn\u0027t exist. Default is true.",
"description": "Create collection during initialisation if it doesn\u0027t exist. Default is true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -151,7 +152,7 @@
},
"database": {
"displayName": "Database",
"description": "Sets the name of the MongoDB database to target",
"description": "Sets the name of the MongoDB database to target For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -166,7 +167,7 @@
},
"operation": {
"displayName": "Operation",
"description": "Sets the operation this endpoint will execute against MongoDB.",
"description": "Sets the operation this endpoint will execute against MongoDB. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -200,7 +201,7 @@
},
"outputType": {
"displayName": "Output Type",
"description": "Convert the output of the producer to the selected type : DocumentList Document or MongoIterable. DocumentList or MongoIterable applies to findAll and aggregate. Document applies to all other operations.",
"description": "Convert the output of the producer to the selected type : DocumentList Document or MongoIterable. DocumentList or MongoIterable applies to findAll and aggregate. Document applies to all other operations. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "common",
"type": "string",
"kind": "parameter",
@ -223,7 +224,7 @@
},
"consumerType": {
"displayName": "Consumer Type",
"description": "Consumer type.",
"description": "Consumer type. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"kind": "parameter",
@ -238,7 +239,7 @@
},
"exceptionHandler": {
"displayName": "Exception Handler",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -254,7 +255,7 @@
},
"exchangePattern": {
"displayName": "Exchange Pattern",
"description": "Sets the exchange pattern when the consumer creates an exchange.",
"description": "Sets the exchange pattern when the consumer creates an exchange. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"kind": "parameter",
@ -277,7 +278,7 @@
},
"cursorRegenerationDelay": {
"displayName": "Cursor Regeneration Delay",
"description": "MongoDB tailable cursors will block until new data arrives. If no new data is inserted, after some time the cursor will be automatically freed and closed by the MongoDB server. The client is expected to regenerate the cursor if needed. This value specifies the time to wait before attempting to fetch a new cursor, and if the attempt fails, how long before the next attempt is made. Default value is 1000ms.",
"description": "MongoDB tailable cursors will block until new data arrives. If no new data is inserted, after some time the cursor will be automatically freed and closed by the MongoDB server. The client is expected to regenerate the cursor if needed. This value specifies the time to wait before attempting to fetch a new cursor, and if the attempt fails, how long before the next attempt is made. Default value is 1000ms. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -293,7 +294,7 @@
},
"dynamicity": {
"displayName": "Dynamicity",
"description": "Sets whether this endpoint will attempt to dynamically resolve the target database and collection from the incoming Exchange properties. Can be used to override at runtime the database and collection specified on the otherwise static endpoint URI. It is disabled by default to boost performance. Enabling it will take a minimal performance hit.",
"description": "Sets whether this endpoint will attempt to dynamically resolve the target database and collection from the incoming Exchange properties. Can be used to override at runtime the database and collection specified on the otherwise static endpoint URI. It is disabled by default to boost performance. Enabling it will take a minimal performance hit. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -309,7 +310,7 @@
},
"readPreference": {
"displayName": "Read Preference",
"description": "Configure how MongoDB clients route read operations to the members of a replica set. Possible values are PRIMARY, PRIMARY_PREFERRED, SECONDARY, SECONDARY_PREFERRED or NEAREST",
"description": "Configure how MongoDB clients route read operations to the members of a replica set. Possible values are PRIMARY, PRIMARY_PREFERRED, SECONDARY, SECONDARY_PREFERRED or NEAREST For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"kind": "parameter",
@ -335,7 +336,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -351,7 +352,7 @@
},
"writeConcern": {
"displayName": "Write Concern",
"description": "Configure the connection bean with the level of acknowledgment requested from MongoDB for write operations to a standalone mongod, replicaset or cluster. Possible values are ACKNOWLEDGED, W1, W2, W3, UNACKNOWLEDGED, JOURNALED or MAJORITY.",
"description": "Configure the connection bean with the level of acknowledgment requested from MongoDB for write operations to a standalone mongod, replicaset or cluster. Possible values are ACKNOWLEDGED, W1, W2, W3, UNACKNOWLEDGED, JOURNALED or MAJORITY. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"kind": "parameter",
@ -379,7 +380,7 @@
},
"writeResultAsHeader": {
"displayName": "Write Result As Header",
"description": "In write operations, it determines whether instead of returning WriteResult as the body of the OUT message, we transfer the IN message to the OUT and attach the WriteResult as a header.",
"description": "In write operations, it determines whether instead of returning WriteResult as the body of the OUT message, we transfer the IN message to the OUT and attach the WriteResult as a header. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -395,7 +396,7 @@
},
"streamFilter": {
"displayName": "Stream Filter",
"description": "Filter condition for change streams consumer.",
"description": "Filter condition for change streams consumer. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "changeStream",
"type": "string",
"kind": "parameter",
@ -410,7 +411,7 @@
},
"persistentId": {
"displayName": "Persistent Id",
"description": "One tail tracking collection can host many trackers for several tailable consumers. To keep them separate, each tracker should have its own unique persistentId.",
"description": "One tail tracking collection can host many trackers for several tailable consumers. To keep them separate, each tracker should have its own unique persistentId. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "string",
"kind": "parameter",
@ -425,7 +426,7 @@
},
"persistentTailTracking": {
"displayName": "Persistent Tail Tracking",
"description": "Enable persistent tail tracking, which is a mechanism to keep track of the last consumed message across system restarts. The next time the system is up, the endpoint will recover the cursor from the point where it last stopped slurping records.",
"description": "Enable persistent tail tracking, which is a mechanism to keep track of the last consumed message across system restarts. The next time the system is up, the endpoint will recover the cursor from the point where it last stopped slurping records. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "boolean",
"kind": "parameter",
@ -441,7 +442,7 @@
},
"tailTrackCollection": {
"displayName": "Tail Track Collection",
"description": "Collection where tail tracking information will be persisted. If not specified, MongoDbTailTrackingConfig#DEFAULT_COLLECTION will be used by default.",
"description": "Collection where tail tracking information will be persisted. If not specified, MongoDbTailTrackingConfig#DEFAULT_COLLECTION will be used by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "string",
"kind": "parameter",
@ -456,7 +457,7 @@
},
"tailTrackDb": {
"displayName": "Tail Track Db",
"description": "Indicates what database the tail tracking mechanism will persist to. If not specified, the current database will be picked by default. Dynamicity will not be taken into account even if enabled, i.e. the tail tracking database will not vary past endpoint initialisation.",
"description": "Indicates what database the tail tracking mechanism will persist to. If not specified, the current database will be picked by default. Dynamicity will not be taken into account even if enabled, i.e. the tail tracking database will not vary past endpoint initialisation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "string",
"kind": "parameter",
@ -471,7 +472,7 @@
},
"tailTrackField": {
"displayName": "Tail Track Field",
"description": "Field where the last tracked value will be placed. If not specified, MongoDbTailTrackingConfig#DEFAULT_FIELD will be used by default.",
"description": "Field where the last tracked value will be placed. If not specified, MongoDbTailTrackingConfig#DEFAULT_FIELD will be used by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "string",
"kind": "parameter",
@ -486,7 +487,7 @@
},
"tailTrackIncreasingField": {
"displayName": "Tail Track Increasing Field",
"description": "Correlation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. The cursor will be (re)created with a query of type: tailTrackIncreasingField greater than lastValue (possibly recovered from persistent tail tracking). Can be of type Integer, Date, String, etc. NOTE: No support for dot notation at the current time, so the field should be at the top level of the document.",
"description": "Correlation field in the incoming record which is of increasing nature and will be used to position the tailing cursor every time it is generated. The cursor will be (re)created with a query of type: tailTrackIncreasingField greater than lastValue (possibly recovered from persistent tail tracking). Can be of type Integer, Date, String, etc. NOTE: No support for dot notation at the current time, so the field should be at the top level of the document. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/mongodb-component.html\">Camel docs</a>",
"label": "tail",
"type": "string",
"kind": "parameter",
@ -1159,10 +1160,20 @@
}
],
"connectionString": {
"displayName": "Connection String",
"description": "The connection string to be passed to mongodb to establish a connection. Examples: 'mongodb://entaxy:entaxy@localhost:27017/'",
"type": "String",
"group": "mongoConnection",
"required": false
}
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeNames":["connectionString"],
"includePatterns":[]
}
}
},
"path": {
@ -1265,4 +1276,4 @@
}
}
}
}
}

View File

@ -9,7 +9,7 @@
"fields": {
"bridgeErrorHandler": {
"displayName": "Bridge Error Handler",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -34,7 +34,7 @@
},
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -59,7 +59,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -84,7 +84,7 @@
},
"host": {
"displayName": "Host",
"description": "Hostname of the FTP server",
"description": "Hostname of the FTP server For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -101,7 +101,7 @@
},
"port": {
"displayName": "Port",
"description": "Port of the FTP server",
"description": "Port of the FTP server For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "number",
"kind": "path",
@ -117,7 +117,7 @@
},
"directoryName": {
"displayName": "Directory Name",
"description": "The starting directory",
"description": "The starting directory For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -133,7 +133,7 @@
},
"binary": {
"displayName": "Binary",
"description": "Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false).",
"description": "Specifies the file transfer mode, BINARY or ASCII. Default is ASCII (false). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -150,7 +150,7 @@
},
"charset": {
"displayName": "Charset",
"description": "This option is used to specify the encoding of the file. You can use this on the consumer, to specify the encodings of the files, which allow Camel to know the charset it should load the file content in case the file content is being accessed. Likewise when writing a file, you can use this option to specify which charset to write the file as well. Do mind that when writing the file Camel may have to read the message content into memory to be able to convert the data into the configured charset, so do not use this if you have big messages.",
"description": "This option is used to specify the encoding of the file. You can use this on the consumer, to specify the encodings of the files, which allow Camel to know the charset it should load the file content in case the file content is being accessed. Likewise when writing a file, you can use this option to specify which charset to write the file as well. Do mind that when writing the file Camel may have to read the message content into memory to be able to convert the data into the configured charset, so do not use this if you have big messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -165,7 +165,7 @@
},
"disconnect": {
"displayName": "Disconnect",
"description": "Whether or not to disconnect from remote FTP server right after use. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead.",
"description": "Whether or not to disconnect from remote FTP server right after use. Disconnect will only disconnect the current connection to the FTP server. If you have a consumer which you want to stop, then you need to stop the consumer/route instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "common",
"type": "boolean",
"kind": "parameter",
@ -181,7 +181,7 @@
},
"doneFileName": {
"displayName": "Done File Name",
"description": "Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders.The done file is always expected in the same folder as the original file. Only ${file.name} and ${file.name.next} is supported as dynamic placeholders.",
"description": "Producer: If provided, then Camel will write a 2nd done file when the original file has been written. The done file will be empty. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders. The done file will always be written in the same folder as the original file. Consumer: If provided, Camel will only consume files if a done file exists. This option configures what file name to use. Either you can specify a fixed name. Or you can use dynamic placeholders.The done file is always expected in the same folder as the original file. Only ${file.name} and ${file.name.next} is supported as dynamic placeholders. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -196,7 +196,7 @@
},
"fileName": {
"displayName": "File Name",
"description": "Use Expression such as File Language to dynamically set the filename. For consumers, it\u0027s used as a filename filter. For producers, it\u0027s used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today\u0027s file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt. The producers support the CamelOverruleFileName header which takes precedence over any existing CamelFileName header; the CamelOverruleFileName is a header that is used only once, and makes it easier as this avoids to temporary store CamelFileName and have to restore it afterwards.",
"description": "Use Expression such as File Language to dynamically set the filename. For consumers, it\u0027s used as a filename filter. For producers, it\u0027s used to evaluate the filename to write. If an expression is set, it take precedence over the CamelFileName header. (Note: The header itself can also be an Expression). The expression options support both String and Expression types. If the expression is a String type, it is always evaluated using the File Language. If the expression is an Expression type, the specified Expression type is used - this allows you, for instance, to use OGNL expressions. For the consumer, you can use it to filter filenames, so you can for instance consume today\u0027s file using the File Language syntax: mydata-${date:now:yyyyMMdd}.txt. The producers support the CamelOverruleFileName header which takes precedence over any existing CamelFileName header; the CamelOverruleFileName is a header that is used only once, and makes it easier as this avoids to temporary store CamelFileName and have to restore it afterwards. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "parameter",
@ -211,7 +211,7 @@
},
"passiveMode": {
"displayName": "Passive Mode",
"description": "Sets passive mode connections. Default is active mode connections.",
"description": "Sets passive mode connections. Default is active mode connections. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "boolean",
"kind": "parameter",
@ -228,7 +228,7 @@
},
"separator": {
"displayName": "Separator",
"description": "Sets the path separator to be used. UNIX \u003d Uses unix style path separator Windows \u003d Uses windows style path separator Auto \u003d (is default) Use existing path separator in file name",
"description": "Sets the path separator to be used. UNIX \u003d Uses unix style path separator Windows \u003d Uses windows style path separator Auto \u003d (is default) Use existing path separator in file name For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "",
"type": "object",
"kind": "parameter",
@ -253,7 +253,7 @@
},
"fastExistsCheck": {
"displayName": "Fast Exists Check",
"description": "If set this option to be true, camel-ftp will use the list file directly to check if the file exists. Since some FTP server may not support to list the file directly, if the option is false, camel-ftp will use the old way to list the directory and check if the file exists. This option also influences readLock\u003dchanged to control whether it performs a fast check to update file information or not. This can be used to speed up the process if the FTP server has a lot of files.",
"description": "If set this option to be true, camel-ftp will use the list file directly to check if the file exists. Since some FTP server may not support to list the file directly, if the option is false, camel-ftp will use the old way to list the directory and check if the file exists. This option also influences readLock\u003dchanged to control whether it performs a fast check to update file information or not. This can be used to speed up the process if the FTP server has a lot of files. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "common,advanced",
"type": "boolean",
"kind": "parameter",
@ -269,7 +269,7 @@
},
"delete": {
"displayName": "Delete",
"description": "If true, the file will be deleted after it is processed successfully.",
"description": "If true, the file will be deleted after it is processed successfully. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -285,7 +285,7 @@
},
"moveFailed": {
"displayName": "Move Failed",
"description": "Sets the move failure expression based on Simple language. For example, to move files into a .error subdirectory use: .error. Note: When moving the files to the fail location Camel will handle the error and will not pick up the file again.",
"description": "Sets the move failure expression based on Simple language. For example, to move files into a .error subdirectory use: .error. Note: When moving the files to the fail location Camel will handle the error and will not pick up the file again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"kind": "parameter",
@ -300,7 +300,7 @@
},
"noop": {
"displayName": "Noop",
"description": "If true, the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop\u003dtrue, Camel will set idempotent\u003dtrue as well, to avoid consuming the same files over and over again.",
"description": "If true, the file is not moved or deleted in any way. This option is good for readonly data, or for ETL type requirements. If noop\u003dtrue, Camel will set idempotent\u003dtrue as well, to avoid consuming the same files over and over again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -316,7 +316,7 @@
},
"preMove": {
"displayName": "Pre Move",
"description": "Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order.",
"description": "Expression (such as File Language) used to dynamically set the filename when moving it before processing. For example to move in-progress files into the order directory set this value to order. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "string",
"kind": "parameter",
@ -331,7 +331,7 @@
},
"preSort": {
"displayName": "Pre Sort",
"description": "When pre-sort is enabled then the consumer will sort the file and directory names during polling, that was retrieved from the file system. You may want to do this in case you need to operate on the files in a sorted order. The pre-sort is executed before the consumer starts to filter, and accept files to process by Camel. This option is default\u003dfalse meaning disabled.",
"description": "When pre-sort is enabled then the consumer will sort the file and directory names during polling, that was retrieved from the file system. You may want to do this in case you need to operate on the files in a sorted order. The pre-sort is executed before the consumer starts to filter, and accept files to process by Camel. This option is default\u003dfalse meaning disabled. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -347,7 +347,7 @@
},
"recursive": {
"displayName": "Recursive",
"description": "If a directory, will look for files in all the sub-directories as well.",
"description": "If a directory, will look for files in all the sub-directories as well. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -363,7 +363,7 @@
},
"sendEmptyMessageWhenIdle": {
"displayName": "Send Empty Message When Idle",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -379,7 +379,7 @@
},
"streamDownload": {
"displayName": "Stream Download",
"description": "Sets the download method to use when not using a local working directory. If set to true, the remote files are streamed to the route as they are read. When set to false, the remote files are loaded into memory before being sent into the route. If enabling this option then you must set stepwise\u003dfalse as both cannot be enabled at the same time.",
"description": "Sets the download method to use when not using a local working directory. If set to true, the remote files are streamed to the route as they are read. When set to false, the remote files are loaded into memory before being sent into the route. If enabling this option then you must set stepwise\u003dfalse as both cannot be enabled at the same time. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -396,7 +396,7 @@
},
"download": {
"displayName": "Download",
"description": "Whether the FTP consumer should download the file. If this option is set to false, then the message body will be null, but the consumer will still trigger a Camel Exchange that has details about the file such as file name, file size, etc. It\u0027s just that the file will not be downloaded.",
"description": "Whether the FTP consumer should download the file. If this option is set to false, then the message body will be null, but the consumer will still trigger a Camel Exchange that has details about the file such as file name, file size, etc. It\u0027s just that the file will not be downloaded. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -412,7 +412,7 @@
},
"exceptionHandler": {
"displayName": "Exception Handler",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -428,7 +428,7 @@
},
"exchangePattern": {
"displayName": "Exchange Pattern",
"description": "Sets the exchange pattern when the consumer creates an exchange.",
"description": "Sets the exchange pattern when the consumer creates an exchange. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -451,7 +451,7 @@
},
"ignoreFileNotFoundOrPermissionError": {
"displayName": "Ignore File Not Found Or Permission Error",
"description": "Whether to ignore when (trying to list files in directories or when downloading a file), which does not exist or due to permission error. By default when a directory or file does not exists or insufficient permission, then an exception is thrown. Setting this option to true allows to ignore that instead.",
"description": "Whether to ignore when (trying to list files in directories or when downloading a file), which does not exist or due to permission error. By default when a directory or file does not exists or insufficient permission, then an exception is thrown. Setting this option to true allows to ignore that instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -468,7 +468,7 @@
},
"inProgressRepository": {
"displayName": "In Progress Repository",
"description": "A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used.",
"description": "A pluggable in-progress repository org.apache.camel.spi.IdempotentRepository. The in-progress repository is used to account the current in progress files being consumed. By default a memory based repository is used. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -483,7 +483,7 @@
},
"localWorkDirectory": {
"displayName": "Local Work Directory",
"description": "When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory.",
"description": "When consuming, a local work directory can be used to store the remote file content directly in local files, to avoid loading the content into memory. This is beneficial, if you consume a very big remote file and thus can conserve memory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "string",
"kind": "parameter",
@ -498,7 +498,7 @@
},
"onCompletionExceptionHandler": {
"displayName": "On Completion Exception Handler",
"description": "To use a custom org.apache.camel.spi.ExceptionHandler to handle any thrown exceptions that happens during the file on completion process where the consumer does either a commit or rollback. The default implementation will log any exception at WARN level and ignore.",
"description": "To use a custom org.apache.camel.spi.ExceptionHandler to handle any thrown exceptions that happens during the file on completion process where the consumer does either a commit or rollback. The default implementation will log any exception at WARN level and ignore. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -513,7 +513,7 @@
},
"pollStrategy": {
"displayName": "Poll Strategy",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -528,7 +528,7 @@
},
"processStrategy": {
"displayName": "Process Strategy",
"description": "A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply.",
"description": "A pluggable org.apache.camel.component.file.GenericFileProcessStrategy allowing you to implement your own readLock option or similar. Can also be used when special conditions must be met before a file can be consumed, such as a special ready file exists. If this option is set then the readLock option does not apply. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -542,7 +542,7 @@
},
"useList": {
"displayName": "Use List",
"description": "Whether to allow using LIST command when downloading a file. Default is true. In some use cases you may want to download a specific file and are not allowed to use the LIST command, and therefore you can set this option to false. Notice when using this option, then the specific file to download does not include meta-data information such as file size, timestamp, permissions etc, because those information is only possible to retrieve when LIST command is in use.",
"description": "Whether to allow using LIST command when downloading a file. Default is true. In some use cases you may want to download a specific file and are not allowed to use the LIST command, and therefore you can set this option to false. Notice when using this option, then the specific file to download does not include meta-data information such as file size, timestamp, permissions etc, because those information is only possible to retrieve when LIST command is in use. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "boolean",
"kind": "parameter",
@ -559,7 +559,7 @@
},
"fileExist": {
"displayName": "File Exist",
"description": "What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. The option eagerDeleteTargetFile can be used to control what to do if an moving the file, and there exists already an existing file, otherwise causing the move operation to fail. The Move option will move any existing files, before writing the target file. - TryRename is only applicable if tempFileName option is in use. This allows to try renaming the file from the temporary name to the actual name, without doing any exists check. This check may be faster on some file systems and especially FTP servers.",
"description": "What to do if a file already exists with the same name. Override, which is the default, replaces the existing file. - Append - adds content to the existing file. - Fail - throws a GenericFileOperationException, indicating that there is already an existing file. - Ignore - silently ignores the problem and does not override the existing file, but assumes everything is okay. - Move - option requires to use the moveExisting option to be configured as well. The option eagerDeleteTargetFile can be used to control what to do if an moving the file, and there exists already an existing file, otherwise causing the move operation to fail. The Move option will move any existing files, before writing the target file. - TryRename is only applicable if tempFileName option is in use. This allows to try renaming the file from the temporary name to the actual name, without doing any exists check. This check may be faster on some file systems and especially FTP servers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "object",
"kind": "parameter",
@ -586,7 +586,7 @@
},
"flatten": {
"displayName": "Flatten",
"description": "Flatten is used to flatten the file name path to strip any leading paths, so it\u0027s just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths.",
"description": "Flatten is used to flatten the file name path to strip any leading paths, so it\u0027s just the file name. This allows you to consume recursively into sub-directories, but when you eg write the files to another directory they will be written in a single directory. Setting this to true on the producer enforces that any file name in CamelFileName header will be stripped for any leading paths. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"kind": "parameter",
@ -602,7 +602,7 @@
},
"jailStartingDirectory": {
"displayName": "Jail Starting Directory",
"description": "Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders.",
"description": "Used for jailing (restricting) writing files to the starting directory (and sub) only. This is enabled by default to not allow Camel to write files to outside directories (to be more secured out of the box). You can turn this off to allow writing files to directories outside the starting directory, such as parent or root folders. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"kind": "parameter",
@ -618,7 +618,7 @@
},
"moveExisting": {
"displayName": "Move Existing",
"description": "Expression (such as File Language) used to compute file name to use when fileExist\u003dMove is configured. To move files into a backup subdirectory just enter backup. This option only supports the following File Language tokens: file:name, file:name.ext, file:name.noext, file:onlyname, file:onlyname.noext, file:ext, and file:parent. Notice the file:parent is not supported by the FTP component, as the FTP component can only move any existing files to a relative directory based on current dir as base.",
"description": "Expression (such as File Language) used to compute file name to use when fileExist\u003dMove is configured. To move files into a backup subdirectory just enter backup. This option only supports the following File Language tokens: file:name, file:name.ext, file:name.noext, file:onlyname, file:onlyname.noext, file:ext, and file:parent. Notice the file:parent is not supported by the FTP component, as the FTP component can only move any existing files to a relative directory based on current dir as base. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -633,7 +633,7 @@
},
"tempFileName": {
"displayName": "Temp File Name",
"description": "The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option \u0027fileName\u0027, not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir.",
"description": "The same as tempPrefix option but offering a more fine grained control on the naming of the temporary filename as it uses the File Language. The location for tempFilename is relative to the final file location in the option \u0027fileName\u0027, not the target directory in the base uri. For example if option fileName includes a directory prefix: dir/finalFilename then tempFileName is relative to that subdirectory dir. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -648,7 +648,7 @@
},
"tempPrefix": {
"displayName": "Temp Prefix",
"description": "This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files.",
"description": "This option is used to write the file using a temporary name and then, after the write is complete, rename it to the real name. Can be used to identify files being written and also avoid consumers (not using exclusive read locks) reading in progress files. Is often used by FTP when uploading big files. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -663,7 +663,7 @@
},
"allowNullBody": {
"displayName": "Allow Null Body",
"description": "Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of \u0027Cannot write null body to file.\u0027 will be thrown. If the fileExist option is set to \u0027Override\u0027, then the file will be truncated, and if set to append the file will remain unchanged.",
"description": "Used to specify if a null body is allowed during file writing. If set to true then an empty file will be created, when set to false, and attempting to send a null body to the file component, a GenericFileWriteException of \u0027Cannot write null body to file.\u0027 will be thrown. If the fileExist option is set to \u0027Override\u0027, then the file will be truncated, and if set to append the file will remain unchanged. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -679,7 +679,7 @@
},
"chmod": {
"displayName": "Chmod",
"description": "Allows you to set chmod on the stored file. For example chmod\u003d640.",
"description": "Allows you to set chmod on the stored file. For example chmod\u003d640. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "string",
"kind": "parameter",
@ -695,7 +695,7 @@
},
"disconnectOnBatchComplete": {
"displayName": "Disconnect On Batch Complete",
"description": "Whether or not to disconnect from remote FTP server right after a Batch upload is complete. disconnectOnBatchComplete will only disconnect the current connection to the FTP server.",
"description": "Whether or not to disconnect from remote FTP server right after a Batch upload is complete. disconnectOnBatchComplete will only disconnect the current connection to the FTP server. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -711,7 +711,7 @@
},
"eagerDeleteTargetFile": {
"displayName": "Eager Delete Target File",
"description": "Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists\u003dOverride and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename. This option is also used to control whether to delete any existing files when fileExist\u003dMove is enabled, and an existing file exists. If this option copyAndDeleteOnRenameFails false, then an exception will be thrown if an existing file existed, if its true, then the existing file is deleted before the move operation.",
"description": "Whether or not to eagerly delete any existing target file. This option only applies when you use fileExists\u003dOverride and the tempFileName option as well. You can use this to disable (set it to false) deleting the target file before the temp file is written. For example you may write big files and want the target file to exists during the temp file is being written. This ensure the target file is only deleted until the very last moment, just before the temp file is being renamed to the target filename. This option is also used to control whether to delete any existing files when fileExist\u003dMove is enabled, and an existing file exists. If this option copyAndDeleteOnRenameFails false, then an exception will be thrown if an existing file existed, if its true, then the existing file is deleted before the move operation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -727,7 +727,7 @@
},
"keepLastModified": {
"displayName": "Keep Last Modified",
"description": "Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers.",
"description": "Will keep the last modified timestamp from the source file (if any). Will use the Exchange.FILE_LAST_MODIFIED header to located the timestamp. This header can contain either a java.util.Date or long with the timestamp. If the timestamp exists and the option is enabled it will set this timestamp on the written file. Note: This option only applies to the file producer. You cannot use this option with any of the ftp producers. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -743,7 +743,7 @@
},
"moveExistingFileStrategy": {
"displayName": "Move Existing File Strategy",
"description": "Strategy (Custom Strategy) used to move file with special naming token to use when fileExist\u003dMove is configured. By default, there is an implementation used if no custom strategy is provided",
"description": "Strategy (Custom Strategy) used to move file with special naming token to use when fileExist\u003dMove is configured. By default, there is an implementation used if no custom strategy is provided For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "object",
"kind": "parameter",
@ -758,7 +758,7 @@
},
"sendNoop": {
"displayName": "Send Noop",
"description": "Whether to send a noop command as a pre-write check before uploading files to the FTP server. This is enabled by default as a validation of the connection is still valid, which allows to silently re-connect to be able to upload the file. However if this causes problems, you can turn this option off.",
"description": "Whether to send a noop command as a pre-write check before uploading files to the FTP server. This is enabled by default as a validation of the connection is still valid, which allows to silently re-connect to be able to upload the file. However if this causes problems, you can turn this option off. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "producer,advanced",
"type": "boolean",
"kind": "parameter",
@ -776,7 +776,7 @@
},
"autoCreate": {
"displayName": "Auto Create",
"description": "Automatically create missing directories in the file\u0027s pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to.",
"description": "Automatically create missing directories in the file\u0027s pathname. For the file consumer, that means creating the starting directory. For the file producer, it means the directory the files should be written to. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -792,7 +792,7 @@
},
"connectTimeout": {
"displayName": "Connect Timeout",
"description": "Sets the connect timeout for waiting for a connection to be established Used by both FTPClient and JSCH",
"description": "Sets the connect timeout for waiting for a connection to be established Used by both FTPClient and JSCH For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -809,7 +809,7 @@
},
"maximumReconnectAttempts": {
"displayName": "Maximum Reconnect Attempts",
"description": "Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior.",
"description": "Specifies the maximum reconnect attempts Camel performs when it tries to connect to the remote FTP server. Use 0 to disable this behavior. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -824,7 +824,7 @@
},
"reconnectDelay": {
"displayName": "Reconnect Delay",
"description": "Delay in millis Camel will wait before performing a reconnect attempt.",
"description": "Delay in millis Camel will wait before performing a reconnect attempt. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -839,7 +839,7 @@
},
"soTimeout": {
"displayName": "So Timeout",
"description": "Sets the so timeout FTP and FTPS Only for Camel 2.4. SFTP for Camel 2.14.3/2.15.3/2.16 onwards. Is the SocketOptions.SO_TIMEOUT value in millis. Recommended option is to set this to 300000 so as not have a hanged connection. On SFTP this option is set as timeout on the JSCH Session instance.",
"description": "Sets the so timeout FTP and FTPS Only for Camel 2.4. SFTP for Camel 2.14.3/2.15.3/2.16 onwards. Is the SocketOptions.SO_TIMEOUT value in millis. Recommended option is to set this to 300000 so as not have a hanged connection. On SFTP this option is set as timeout on the JSCH Session instance. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -856,7 +856,7 @@
},
"stepwise": {
"displayName": "Stepwise",
"description": "Sets whether we should stepwise change directories while traversing file structures when downloading files, or as well when uploading a file to a directory. You can disable this if you for example are in a situation where you cannot change directory on the FTP server due security reasons. Stepwise cannot be used together with streamDownload.",
"description": "Sets whether we should stepwise change directories while traversing file structures when downloading files, or as well when uploading a file to a directory. You can disable this if you for example are in a situation where you cannot change directory on the FTP server due security reasons. Stepwise cannot be used together with streamDownload. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -873,7 +873,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -889,7 +889,7 @@
},
"throwExceptionOnConnectFailed": {
"displayName": "Throw Exception On Connect Failed",
"description": "Should an exception be thrown if connection failed (exhausted) By default exception is not thrown and a WARN is logged. You can use this to enable exception being thrown and handle the thrown exception from the org.apache.camel.spi.PollingConsumerPollStrategy rollback method.",
"description": "Should an exception be thrown if connection failed (exhausted) By default exception is not thrown and a WARN is logged. You can use this to enable exception being thrown and handle the thrown exception from the org.apache.camel.spi.PollingConsumerPollStrategy rollback method. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -906,7 +906,7 @@
},
"timeout": {
"displayName": "Timeout",
"description": "Sets the data timeout for waiting for reply Used only by FTPClient",
"description": "Sets the data timeout for waiting for reply Used only by FTPClient For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "duration",
"kind": "parameter",
@ -923,7 +923,7 @@
},
"antExclude": {
"displayName": "Ant Exclude",
"description": "Ant style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence over antInclude. Multiple exclusions may be specified in comma-delimited format.",
"description": "Ant style filter exclusion. If both antInclude and antExclude are used, antExclude takes precedence over antInclude. Multiple exclusions may be specified in comma-delimited format. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -938,7 +938,7 @@
},
"antFilterCaseSensitive": {
"displayName": "Ant Filter Case Sensitive",
"description": "Sets case sensitive flag on ant filter.",
"description": "Sets case sensitive flag on ant filter. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -954,7 +954,7 @@
},
"antInclude": {
"displayName": "Ant Include",
"description": "Ant style filter inclusion. Multiple inclusions may be specified in comma-delimited format.",
"description": "Ant style filter inclusion. Multiple inclusions may be specified in comma-delimited format. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -969,7 +969,7 @@
},
"eagerMaxMessagesPerPoll": {
"displayName": "Eager Max Messages Per Poll",
"description": "Allows for controlling whether the limit from maxMessagesPerPoll is eager or not. If eager then the limit is during the scanning of files. Where as false would scan all files, and then perform sorting. Setting this option to false allows for sorting all files first, and then limit the poll. Mind that this requires a higher memory usage as all file details are in memory to perform the sorting.",
"description": "Allows for controlling whether the limit from maxMessagesPerPoll is eager or not. If eager then the limit is during the scanning of files. Where as false would scan all files, and then perform sorting. Setting this option to false allows for sorting all files first, and then limit the poll. Mind that this requires a higher memory usage as all file details are in memory to perform the sorting. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -985,7 +985,7 @@
},
"exclude": {
"displayName": "Exclude",
"description": "Is used to exclude files, if filename matches the regex pattern (matching is case in-senstive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris",
"description": "Is used to exclude files, if filename matches the regex pattern (matching is case in-senstive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1000,7 +1000,7 @@
},
"filter": {
"displayName": "Filter",
"description": "Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method.",
"description": "Pluggable filter as a org.apache.camel.component.file.GenericFileFilter class. Will skip files if filter returns false in its accept() method. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "object",
"kind": "parameter",
@ -1014,7 +1014,7 @@
},
"filterDirectory": {
"displayName": "Filter Directory",
"description": "Filters the directory based on Simple language. For example to filter on current date, you can use a simple date pattern such as ${date:now:yyyMMdd}",
"description": "Filters the directory based on Simple language. For example to filter on current date, you can use a simple date pattern such as ${date:now:yyyMMdd} For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1029,7 +1029,7 @@
},
"filterFile": {
"displayName": "Filter File",
"description": "Filters the file based on Simple language. For example to filter on file size, you can use ${file:size} 5000",
"description": "Filters the file based on Simple language. For example to filter on file size, you can use ${file:size} 5000 For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1044,7 +1044,7 @@
},
"idempotent": {
"displayName": "Idempotent",
"description": "Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop\u003dtrue then idempotent will be enabled as well to avoid consuming the same files over and over again.",
"description": "Option to use the Idempotent Consumer EIP pattern to let Camel skip already processed files. Will by default use a memory based LRUCache that holds 1000 entries. If noop\u003dtrue then idempotent will be enabled as well to avoid consuming the same files over and over again. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "boolean",
"kind": "parameter",
@ -1060,7 +1060,7 @@
},
"idempotentKey": {
"displayName": "Idempotent Key",
"description": "To use a custom idempotent key. By default the absolute path of the file is used. You can use the File Language, for example to use the file name and file size, you can do: idempotentKey\u003d${file:name}-${file:size}",
"description": "To use a custom idempotent key. By default the absolute path of the file is used. You can use the File Language, for example to use the file name and file size, you can do: idempotentKey\u003d${file:name}-${file:size} For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1075,7 +1075,7 @@
},
"idempotentRepository": {
"displayName": "Idempotent Repository",
"description": "A pluggable repository org.apache.camel.spi.IdempotentRepository which by default use MemoryMessageIdRepository if none is specified and idempotent is true.",
"description": "A pluggable repository org.apache.camel.spi.IdempotentRepository which by default use MemoryMessageIdRepository if none is specified and idempotent is true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "object",
"kind": "parameter",
@ -1090,7 +1090,7 @@
},
"include": {
"displayName": "Include",
"description": "Is used to include files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris",
"description": "Is used to include files, if filename matches the regex pattern (matching is case in-sensitive). Notice if you use symbols such as plus sign and others you would need to configure this using the RAW() syntax if configuring this as an endpoint uri. See more details at configuring endpoint uris For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1105,7 +1105,7 @@
},
"maxDepth": {
"displayName": "Max Depth",
"description": "The maximum depth to traverse when recursively processing a directory.",
"description": "The maximum depth to traverse when recursively processing a directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -1121,7 +1121,7 @@
},
"maxMessagesPerPoll": {
"displayName": "Max Messages Per Poll",
"description": "To define a maximum messages to gather per poll. By default no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. Notice: If this option is in use then the File and FTP components will limit before any sorting. For example if you have 100000 files and use maxMessagesPerPoll\u003d500, then only the first 500 files will be picked up, and then sorted. You can use the eagerMaxMessagesPerPoll option and set this to false to allow to scan all files first and then sort afterwards.",
"description": "To define a maximum messages to gather per poll. By default no maximum is set. Can be used to set a limit of e.g. 1000 to avoid when starting up the server that there are thousands of files. Set a value of 0 or negative to disabled it. Notice: If this option is in use then the File and FTP components will limit before any sorting. For example if you have 100000 files and use maxMessagesPerPoll\u003d500, then only the first 500 files will be picked up, and then sorted. You can use the eagerMaxMessagesPerPoll option and set this to false to allow to scan all files first and then sort afterwards. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -1136,7 +1136,7 @@
},
"minDepth": {
"displayName": "Min Depth",
"description": "The minimum depth to start processing when recursively processing a directory. Using minDepth\u003d1 means the base directory. Using minDepth\u003d2 means the first sub directory.",
"description": "The minimum depth to start processing when recursively processing a directory. Using minDepth\u003d1 means the base directory. Using minDepth\u003d2 means the first sub directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "number",
"kind": "parameter",
@ -1151,7 +1151,7 @@
},
"move": {
"displayName": "Move",
"description": "Expression (such as Simple Language) used to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done.",
"description": "Expression (such as Simple Language) used to dynamically set the filename when moving it after processing. To move files into a .done subdirectory just enter .done. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,filter",
"type": "string",
"kind": "parameter",
@ -1166,7 +1166,7 @@
},
"exclusiveReadLockStrategy": {
"displayName": "Exclusive Read Lock Strategy",
"description": "Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation.",
"description": "Pluggable read-lock as a org.apache.camel.component.file.GenericFileExclusiveReadLockStrategy implementation. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "object",
"kind": "parameter",
@ -1180,7 +1180,7 @@
},
"readLock": {
"displayName": "Read Lock",
"description": "Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Camel will wait until the file lock is granted. This option provides the build in strategies: - none - No read lock is in use - markerFile - Camel creates a marker file (fileName.camelLock) and then holds a lock on it. This option is not available for the FTP component - changed - Changed is using file length/modification timestamp to detect whether the file is currently being copied or not. Will at least use 1 sec to determine this, so this option cannot consume files as fast as the others, but can be more reliable as the JDK IO API cannot always determine whether a file is currently being used by another process. The option readLockCheckInterval can be used to set the check frequency. - fileLock - is for using java.nio.channels.FileLock. This option is not avail for Windows OS and the FTP component. This approach should be avoided when accessing a remote file system via a mount/share unless that file system supports distributed file locks. - rename - rename is for using a try to rename the file as a test if we can get exclusive read-lock. - idempotent - (only for file component) idempotent is for using a idempotentRepository as the read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-changed - (only for file component) idempotent-changed is for using a idempotentRepository and changed as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-rename - (only for file component) idempotent-rename is for using a idempotentRepository and rename as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that.Notice: The various read locks is not all suited to work in clustered mode, where concurrent consumers on different nodes is competing for the same files on a shared file system. The markerFile using a close to atomic operation to create the empty marker file, but its not guaranteed to work in a cluster. The fileLock may work better but then the file system need to support distributed file locks, and so on. Using the idempotent read lock can support clustering if the idempotent repository supports clustering, such as Hazelcast Component or Infinispan.",
"description": "Used by consumer, to only poll the files if it has exclusive read-lock on the file (i.e. the file is not in-progress or being written). Camel will wait until the file lock is granted. This option provides the build in strategies: - none - No read lock is in use - markerFile - Camel creates a marker file (fileName.camelLock) and then holds a lock on it. This option is not available for the FTP component - changed - Changed is using file length/modification timestamp to detect whether the file is currently being copied or not. Will at least use 1 sec to determine this, so this option cannot consume files as fast as the others, but can be more reliable as the JDK IO API cannot always determine whether a file is currently being used by another process. The option readLockCheckInterval can be used to set the check frequency. - fileLock - is for using java.nio.channels.FileLock. This option is not avail for Windows OS and the FTP component. This approach should be avoided when accessing a remote file system via a mount/share unless that file system supports distributed file locks. - rename - rename is for using a try to rename the file as a test if we can get exclusive read-lock. - idempotent - (only for file component) idempotent is for using a idempotentRepository as the read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-changed - (only for file component) idempotent-changed is for using a idempotentRepository and changed as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that. - idempotent-rename - (only for file component) idempotent-rename is for using a idempotentRepository and rename as the combined read-lock. This allows to use read locks that supports clustering if the idempotent repository implementation supports that.Notice: The various read locks is not all suited to work in clustered mode, where concurrent consumers on different nodes is competing for the same files on a shared file system. The markerFile using a close to atomic operation to create the empty marker file, but its not guaranteed to work in a cluster. The fileLock may work better but then the file system need to support distributed file locks, and so on. Using the idempotent read lock can support clustering if the idempotent repository supports clustering, such as Hazelcast Component or Infinispan. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "string",
"kind": "parameter",
@ -1209,7 +1209,7 @@
},
"readLockCheckInterval": {
"displayName": "Read Lock Check Interval",
"description": "Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file. Notice: For FTP the default readLockCheckInterval is 5000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit.",
"description": "Interval in millis for the read-lock, if supported by the read lock. This interval is used for sleeping between attempts to acquire the read lock. For example when using the changed read lock, you can set a higher interval period to cater for slow writes. The default of 1 sec. may be too fast if the producer is very slow writing the file. Notice: For FTP the default readLockCheckInterval is 5000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1225,7 +1225,7 @@
},
"readLockDeleteOrphanLockFiles": {
"displayName": "Read Lock Delete Orphan Lock Files",
"description": "Whether or not read lock with marker files should upon startup delete any orphan read lock files, which may have been left on the file system, if Camel was not properly shutdown (such as a JVM crash). If turning this option to false then any orphaned lock file will cause Camel to not attempt to pickup that file, this could also be due another node is concurrently reading files from the same shared directory.",
"description": "Whether or not read lock with marker files should upon startup delete any orphan read lock files, which may have been left on the file system, if Camel was not properly shutdown (such as a JVM crash). If turning this option to false then any orphaned lock file will cause Camel to not attempt to pickup that file, this could also be due another node is concurrently reading files from the same shared directory. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1241,7 +1241,7 @@
},
"readLockLoggingLevel": {
"displayName": "Read Lock Logging Level",
"description": "Logging level used when a read lock could not be acquired. By default a DEBUG is logged. You can change this level, for example to OFF to not have any logging. This option is only applicable for readLock of types: changed, fileLock, idempotent, idempotent-changed, idempotent-rename, rename.",
"description": "Logging level used when a read lock could not be acquired. By default a DEBUG is logged. You can change this level, for example to OFF to not have any logging. This option is only applicable for readLock of types: changed, fileLock, idempotent, idempotent-changed, idempotent-rename, rename. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "object",
"kind": "parameter",
@ -1268,7 +1268,7 @@
},
"readLockMarkerFile": {
"displayName": "Read Lock Marker File",
"description": "Whether to use marker file with the changed, rename, or exclusive read lock types. By default a marker file is used as well to guard against other processes picking up the same files. This behavior can be turned off by setting this option to false. For example if you do not want to write marker files to the file systems by the Camel application.",
"description": "Whether to use marker file with the changed, rename, or exclusive read lock types. By default a marker file is used as well to guard against other processes picking up the same files. This behavior can be turned off by setting this option to false. For example if you do not want to write marker files to the file systems by the Camel application. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1284,7 +1284,7 @@
},
"readLockMinAge": {
"displayName": "Read Lock Min Age",
"description": "This option is applied only for readLock\u003dchanged. It allows to specify a minimum age the file must be before attempting to acquire the read lock. For example use readLockMinAge\u003d300s to require the file is at last 5 minutes old. This can speedup the changed read lock as it will only attempt to acquire files which are at least that given age.",
"description": "This option is applied only for readLock\u003dchanged. It allows to specify a minimum age the file must be before attempting to acquire the read lock. For example use readLockMinAge\u003d300s to require the file is at last 5 minutes old. This can speedup the changed read lock as it will only attempt to acquire files which are at least that given age. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1300,7 +1300,7 @@
},
"readLockMinLength": {
"displayName": "Read Lock Min Length",
"description": "This option is applied only for readLock\u003dchanged. It allows you to configure a minimum file length. By default Camel expects the file to contain data, and thus the default value is 1. You can set this option to zero, to allow consuming zero-length files.",
"description": "This option is applied only for readLock\u003dchanged. It allows you to configure a minimum file length. By default Camel expects the file to contain data, and thus the default value is 1. You can set this option to zero, to allow consuming zero-length files. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1316,7 +1316,7 @@
},
"readLockRemoveOnCommit": {
"displayName": "Read Lock Remove On Commit",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file is succeeded and a commit happens. By default the file is not removed which ensures that any race-condition do not occur so another active node may attempt to grab the file. Instead the idempotent repository may support eviction strategies that you can configure to evict the file name entry after X minutes - this ensures no problems with race conditions. See more details at the readLockIdempotentReleaseDelay option.",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file is succeeded and a commit happens. By default the file is not removed which ensures that any race-condition do not occur so another active node may attempt to grab the file. Instead the idempotent repository may support eviction strategies that you can configure to evict the file name entry after X minutes - this ensures no problems with race conditions. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1332,7 +1332,7 @@
},
"readLockRemoveOnRollback": {
"displayName": "Read Lock Remove On Rollback",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file failed and a rollback happens. If this option is false, then the file name entry is confirmed (as if the file did a commit).",
"description": "This option is applied only for readLock\u003didempotent. It allows to specify whether to remove the file name entry from the idempotent repository when processing the file failed and a rollback happens. If this option is false, then the file name entry is confirmed (as if the file did a commit). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -1348,7 +1348,7 @@
},
"readLockTimeout": {
"displayName": "Read Lock Timeout",
"description": "Optional timeout in millis for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Camel will skip the file. At next poll Camel, will try the file again, and this time maybe the read-lock could be granted. Use a value of 0 or lower to indicate forever. Currently fileLock, changed and rename support the timeout. Notice: For FTP the default readLockTimeout value is 20000 instead of 10000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit.",
"description": "Optional timeout in millis for the read-lock, if supported by the read-lock. If the read-lock could not be granted and the timeout triggered, then Camel will skip the file. At next poll Camel, will try the file again, and this time maybe the read-lock could be granted. Use a value of 0 or lower to indicate forever. Currently fileLock, changed and rename support the timeout. Notice: For FTP the default readLockTimeout value is 20000 instead of 10000. The readLockTimeout value must be higher than readLockCheckInterval, but a rule of thumb is to have a timeout that is at least 2 or more times higher than the readLockCheckInterval. This is needed to ensure that amble time is allowed for the read lock process to try to grab the lock before the timeout was hit. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -1364,7 +1364,7 @@
},
"backoffErrorThreshold": {
"displayName": "Backoff Error Threshold",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1379,7 +1379,7 @@
},
"backoffIdleThreshold": {
"displayName": "Backoff Idle Threshold",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1394,7 +1394,7 @@
},
"backoffMultiplier": {
"displayName": "Backoff Multiplier",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1409,7 +1409,7 @@
},
"delay": {
"displayName": "Delay",
"description": "Milliseconds before the next poll.",
"description": "Milliseconds before the next poll. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1425,7 +1425,7 @@
},
"greedy": {
"displayName": "Greedy",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1441,7 +1441,7 @@
},
"initialDelay": {
"displayName": "Initial Delay",
"description": "Milliseconds before the first poll starts.",
"description": "Milliseconds before the first poll starts. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1457,7 +1457,7 @@
},
"repeatCount": {
"displayName": "Repeat Count",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -1473,7 +1473,7 @@
},
"runLoggingLevel": {
"displayName": "Run Logging Level",
"description": "The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.",
"description": "The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1500,7 +1500,7 @@
},
"scheduledExecutorService": {
"displayName": "Scheduled Executor Service",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1515,7 +1515,7 @@
},
"scheduler": {
"displayName": "Scheduler",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "string",
"kind": "parameter",
@ -1539,7 +1539,7 @@
},
"schedulerProperties": {
"displayName": "Scheduler Properties",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1556,7 +1556,7 @@
},
"startScheduler": {
"displayName": "Start Scheduler",
"description": "Whether the scheduler should be auto started.",
"description": "Whether the scheduler should be auto started. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1572,7 +1572,7 @@
},
"timeUnit": {
"displayName": "Time Unit",
"description": "Time unit for initialDelay and delay options.",
"description": "Time unit for initialDelay and delay options. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -1600,7 +1600,7 @@
},
"useFixedDelay": {
"displayName": "Use Fixed Delay",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1616,9 +1616,9 @@
},
"password": {
"displayName": "Password",
"description": "Password to use for login",
"description": "Password to use for login For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"type": "password",
"kind": "parameter",
"required": false,
"hidden": true,
@ -1632,7 +1632,7 @@
},
"username": {
"displayName": "Username",
"description": "Username to use for login",
"description": "Username to use for login For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -1648,7 +1648,7 @@
},
"shuffle": {
"displayName": "Shuffle",
"description": "To shuffle the list of files (sort in random order)",
"description": "To shuffle the list of files (sort in random order) For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "boolean",
"kind": "parameter",
@ -1664,7 +1664,7 @@
},
"sortBy": {
"displayName": "Sort By",
"description": "Built-in sort by using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date.",
"description": "Built-in sort by using the File Language. Supports nested sorts, so you can have a sort by file name and as a 2nd group sort by modified date. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "string",
"kind": "parameter",
@ -1679,7 +1679,7 @@
},
"sorter": {
"displayName": "Sorter",
"description": "Pluggable sorter as a java.util.Comparator class.",
"description": "Pluggable sorter as a java.util.Comparator class. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/ftp-component.html\">Camel docs</a>",
"label": "consumer,sort",
"type": "object",
"kind": "parameter",
@ -1814,4 +1814,4 @@
}
}
}
}
}

View File

@ -6,7 +6,8 @@
"isAbstract": false,
"camelOriginComponent": "sftp",
"label": "sftp",
"description": "Upload and download files to/from SFTP servers.",
"description": "This component provides access to remote file systems over the FTP and SFTP protocols. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"displayName": "SFTP",
"camelOrigin": "camel-ftp",
"camelOriginJavaType": "org.apache.camel.component.file.remote.SftpComponent"
},
@ -14,7 +15,7 @@
"fields": {
"jschLoggingLevel": {
"displayName": "Jsch Logging Level",
"description": "The logging level to use for JSCH activity logging. As JSCH is verbose at by default at INFO level the threshold is WARN by default.",
"description": "The logging level to use for JSCH activity logging. As JSCH is verbose at by default at INFO level the threshold is WARN by default. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "",
"type": "object",
"kind": "parameter",
@ -43,7 +44,7 @@
},
"bindAddress": {
"displayName": "Bind Address",
"description": "Specifies the address of the local interface against which the connection should bind.",
"description": "Specifies the address of the local interface against which the connection should bind. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"kind": "parameter",
@ -60,7 +61,7 @@
},
"bulkRequests": {
"displayName": "Bulk Requests",
"description": "Specifies how many requests may be outstanding at any one time. Increasing this value may slightly improve file transfer speed but will increase memory usage.",
"description": "Specifies how many requests may be outstanding at any one time. Increasing this value may slightly improve file transfer speed but will increase memory usage. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -77,7 +78,7 @@
},
"compression": {
"displayName": "Compression",
"description": "To use compression. Specify a level from 1 to 10. Important: You must manually add the needed JSCH zlib JAR to the classpath for compression support.",
"description": "To use compression. Specify a level from 1 to 10. Important: You must manually add the needed JSCH zlib JAR to the classpath for compression support. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -94,7 +95,7 @@
},
"existDirCheckUsingLs": {
"displayName": "Exist Dir Check Using Ls",
"description": "Whether to check for existing directory using LS command or CD. By default LS is used which is safer as otherwise Camel needs to change the directory back after checking. However LS has been reported to cause a problem on windows system in some situations and therefore you can disable this option to use CD.",
"description": "Whether to check for existing directory using LS command or CD. By default LS is used which is safer as otherwise Camel needs to change the directory back after checking. However LS has been reported to cause a problem on windows system in some situations and therefore you can disable this option to use CD. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -112,7 +113,7 @@
},
"proxy": {
"displayName": "Proxy",
"description": "To use a custom configured com.jcraft.jsch.Proxy. This proxy is used to consume/send messages from the target SFTP host.",
"description": "To use a custom configured com.jcraft.jsch.Proxy. This proxy is used to consume/send messages from the target SFTP host. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "parameter",
@ -127,7 +128,7 @@
},
"serverAliveCountMax": {
"displayName": "Server Alive Count Max",
"description": "Sets the number of keep-alive messages which may be sent without receiving any messages back from the server. If this threshold is reached while keep-alive messages are being sent, the connection will be disconnected. The default value is one.",
"description": "Sets the number of keep-alive messages which may be sent without receiving any messages back from the server. If this threshold is reached while keep-alive messages are being sent, the connection will be disconnected. The default value is one. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -145,7 +146,7 @@
},
"serverAliveInterval": {
"displayName": "Server Alive Interval",
"description": "Sets the interval (millis) to send a keep-alive message. If zero is specified, any keep-alive message must not be sent. The default interval is zero.",
"description": "Sets the interval (millis) to send a keep-alive message. If zero is specified, any keep-alive message must not be sent. The default interval is zero. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -162,7 +163,7 @@
},
"readLockIdempotentReleaseAsync": {
"displayName": "Read Lock Idempotent Release Async",
"description": "Whether the delayed release task should be synchronous or asynchronous. See more details at the readLockIdempotentReleaseDelay option.",
"description": "Whether the delayed release task should be synchronous or asynchronous. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "boolean",
"kind": "parameter",
@ -178,7 +179,7 @@
},
"readLockIdempotentReleaseAsyncPoolSize": {
"displayName": "Read Lock Idempotent Release Async Pool Size",
"description": "The number of threads in the scheduled thread pool when using asynchronous release tasks. Using a default of 1 core threads should be sufficient in almost all use-cases, only set this to a higher value if either updating the idempotent repository is slow, or there are a lot of files to process. This option is not in-use if you use a shared thread pool by configuring the readLockIdempotentReleaseExecutorService option. See more details at the readLockIdempotentReleaseDelay option.",
"description": "The number of threads in the scheduled thread pool when using asynchronous release tasks. Using a default of 1 core threads should be sufficient in almost all use-cases, only set this to a higher value if either updating the idempotent repository is slow, or there are a lot of files to process. This option is not in-use if you use a shared thread pool by configuring the readLockIdempotentReleaseExecutorService option. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -193,7 +194,7 @@
},
"readLockIdempotentReleaseDelay": {
"displayName": "Read Lock Idempotent Release Delay",
"description": "Whether to delay the release task for a period of millis. This can be used to delay the release tasks to expand the window when a file is regarded as read-locked, in an active/active cluster scenario with a shared idempotent repository, to ensure other nodes cannot potentially scan and acquire the same file, due to race-conditions. By expanding the time-window of the release tasks helps prevents these situations. Note delaying is only needed if you have configured readLockRemoveOnCommit to true.",
"description": "Whether to delay the release task for a period of millis. This can be used to delay the release tasks to expand the window when a file is regarded as read-locked, in an active/active cluster scenario with a shared idempotent repository, to ensure other nodes cannot potentially scan and acquire the same file, due to race-conditions. By expanding the time-window of the release tasks helps prevents these situations. Note delaying is only needed if you have configured readLockRemoveOnCommit to true. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "number",
"kind": "parameter",
@ -208,7 +209,7 @@
},
"readLockIdempotentReleaseExecutorService": {
"displayName": "Read Lock Idempotent Release Executor Service",
"description": "To use a custom and shared thread pool for asynchronous release tasks. See more details at the readLockIdempotentReleaseDelay option.",
"description": "To use a custom and shared thread pool for asynchronous release tasks. See more details at the readLockIdempotentReleaseDelay option. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "consumer,lock",
"type": "object",
"kind": "parameter",
@ -223,7 +224,7 @@
},
"ciphers": {
"displayName": "Ciphers",
"description": "Set a comma separated list of ciphers that will be used in order of preference. Possible cipher names are defined by JCraft JSCH. Some examples include: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc. If not specified the default list from JSCH will be used.",
"description": "Set a comma separated list of ciphers that will be used in order of preference. Possible cipher names are defined by JCraft JSCH. Some examples include: aes128-ctr,aes128-cbc,3des-ctr,3des-cbc,blowfish-cbc,aes192-cbc,aes256-cbc. If not specified the default list from JSCH will be used. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -240,7 +241,7 @@
},
"keyPair": {
"displayName": "Key Pair",
"description": "Sets a key pair of the public and private key so to that the SFTP endpoint can do public/private key verification.",
"description": "Sets a key pair of the public and private key so to that the SFTP endpoint can do public/private key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "object",
"kind": "parameter",
@ -257,7 +258,7 @@
},
"knownHosts": {
"displayName": "Known Hosts",
"description": "Sets the known_hosts from the byte array, so that the SFTP endpoint can do host key verification.",
"description": "Sets the known_hosts from the byte array, so that the SFTP endpoint can do host key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -274,7 +275,7 @@
},
"knownHostsFile": {
"displayName": "Known Hosts File",
"description": "Sets the known_hosts file, so that the SFTP endpoint can do host key verification.",
"description": "Sets the known_hosts file, so that the SFTP endpoint can do host key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -291,7 +292,7 @@
},
"knownHostsUri": {
"displayName": "Known Hosts Uri",
"description": "Sets the known_hosts file (loaded from classpath by default), so that the SFTP endpoint can do host key verification.",
"description": "Sets the known_hosts file (loaded from classpath by default), so that the SFTP endpoint can do host key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -308,7 +309,7 @@
},
"preferredAuthentications": {
"displayName": "Preferred Authentications",
"description": "Set the preferred authentications which SFTP endpoint will used. Some example include:password,publickey. If not specified the default list from JSCH will be used.",
"description": "Set the preferred authentications which SFTP endpoint will used. Some example include:password,publickey. If not specified the default list from JSCH will be used. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -325,7 +326,7 @@
},
"privateKey": {
"displayName": "Private Key",
"description": "Set the private key as byte so that the SFTP endpoint can do private key verification.",
"description": "Set the private key as byte so that the SFTP endpoint can do private key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -342,7 +343,7 @@
},
"privateKeyFile": {
"displayName": "Private Key File",
"description": "Set the private key file so that the SFTP endpoint can do private key verification.",
"description": "Set the private key file so that the SFTP endpoint can do private key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -359,7 +360,7 @@
},
"privateKeyPassphrase": {
"displayName": "Private Key Passphrase",
"description": "Set the private key file passphrase so that the SFTP endpoint can do private key verification.",
"description": "Set the private key file passphrase so that the SFTP endpoint can do private key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -376,7 +377,7 @@
},
"privateKeyUri": {
"displayName": "Private Key Uri",
"description": "Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification.",
"description": "Set the private key file (loaded from classpath by default) so that the SFTP endpoint can do private key verification. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -393,7 +394,7 @@
},
"strictHostKeyChecking": {
"displayName": "Strict Host Key Checking",
"description": "Sets whether to use strict host key checking.",
"description": "Sets whether to use strict host key checking. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"kind": "parameter",
@ -418,7 +419,7 @@
},
"useUserKnownHostsFile": {
"displayName": "Use User Known Hosts File",
"description": "If knownHostFile has not been explicit configured then use the host file from System.getProperty(user.home)/.ssh/known_hosts",
"description": "If knownHostFile has not been explicit configured then use the host file from System.getProperty(user.home)/.ssh/known_hosts For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/sftp-component.html\">Camel docs</a>",
"label": "security",
"type": "boolean",
"kind": "parameter",
@ -433,13 +434,6 @@
"configurationClass": "org.apache.camel.component.file.remote.SftpConfiguration",
"configurationField": "configuration"
}
},
"connectionString": {
"displayName": "Connection String",
"description": "Format: [username@]hostname[:port]/directoryname",
"type": "String",
"required": true,
"group": "entaxy"
}
},
"##camel": {
@ -2223,7 +2217,7 @@
"group": "security",
"label": "security",
"required": false,
"type": "string",
"type": "password",
"javaType": "java.lang.String",
"deprecated": false,
"secret": true,
@ -2392,7 +2386,11 @@
"outputs": {
"init": {
"fields": {
"connectionString": {},
"username": {},
"password": {},
"host": {},
"port": {},
"directoryName": {},
"@IMPORT": [
{
"sourceFactoryId": "#",
@ -2410,6 +2408,15 @@
}
}
]
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeTypes":["string","password","number"],
"includeNames":["username","password","host","port","directoryName"],
"includePatterns":[]
}
}
},
"path": {

View File

@ -6,7 +6,8 @@
"isAbstract": false,
"camelOriginComponent": "telegram",
"label": "cloud,api,chat,telegram",
"description": "Send and receive messages acting as a Telegram Bot Telegram Bot API.",
"description": "The Telegram component provides access to the Telegram Bot API. It allows a Camel-based application to send and receive messages by acting as a Bot, participating in direct conversations with normal users, private and public groups or channels. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"displayName": "TELEGRAM",
"camelOrigin": "camel-telegram",
"camelOriginJavaType": "org.apache.camel.component.telegram.TelegramComponent"
},
@ -14,7 +15,7 @@
"fields": {
"bridgeErrorHandler": {
"displayName": "Bridge Error Handler",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"required": false,
@ -39,7 +40,7 @@
},
"lazyStartProducer": {
"displayName": "Lazy Start Producer",
"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\u0027s 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.",
"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\u0027s 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. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "producer",
"type": "boolean",
"required": false,
@ -64,7 +65,7 @@
},
"baseUri": {
"displayName": "Base Uri",
"description": "Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API",
"description": "Can be used to set an alternative base URI, e.g. when you want to test the component against a mock Telegram API For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "string",
"required": false,
@ -91,7 +92,7 @@
},
"basicPropertyBinding": {
"displayName": "Basic Property Binding",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities",
"description": "Whether the component should use basic property binding (Camel 2.x) or the newer property binding with additional capabilities For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"required": false,
@ -116,7 +117,7 @@
},
"client": {
"displayName": "Client",
"description": "To use a custom AsyncHttpClient",
"description": "To use a custom AsyncHttpClient For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"kind": "property",
@ -131,7 +132,7 @@
},
"clientConfig": {
"displayName": "Client Config",
"description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance.",
"description": "To configure the AsyncHttpClient to use a custom com.ning.http.client.AsyncHttpClientConfig instance. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "object",
"required": false,
@ -155,7 +156,7 @@
},
"authorizationToken": {
"displayName": "Authorization Token",
"description": "The default Telegram authorization token to be used when the information is not provided in the endpoints.",
"description": "The default Telegram authorization token to be used when the information is not provided in the endpoints. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "security",
"type": "string",
"required": false,
@ -182,7 +183,7 @@
},
"type": {
"displayName": "Type",
"description": "The endpoint type. Currently, only the \u0027bots\u0027 type is supported.",
"description": "The endpoint type. Currently, only the \u0027bots\u0027 type is supported. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "",
"type": "string",
"kind": "path",
@ -206,7 +207,7 @@
},
"limit": {
"displayName": "Limit",
"description": "Limit on the number of updates that can be received in a single polling request.",
"description": "Limit on the number of updates that can be received in a single polling request. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer",
"type": "number",
"kind": "parameter",
@ -225,7 +226,7 @@
},
"sendEmptyMessageWhenIdle": {
"displayName": "Send Empty Message When Idle",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead.",
"description": "If the polling consumer did not poll any files, you can enable this option to send an empty message (no body) instead. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer",
"type": "boolean",
"kind": "parameter",
@ -241,7 +242,7 @@
},
"timeout": {
"displayName": "Timeout",
"description": "Timeout in seconds for long polling. Put 0 for short polling or a bigger number for long polling. Long polling produces shorter response time.",
"description": "Timeout in seconds for long polling. Put 0 for short polling or a bigger number for long polling. Long polling produces shorter response time. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer",
"type": "number",
"kind": "parameter",
@ -260,7 +261,7 @@
},
"exceptionHandler": {
"displayName": "Exception Handler",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored.",
"description": "To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -276,7 +277,7 @@
},
"exchangePattern": {
"displayName": "Exchange Pattern",
"description": "Sets the exchange pattern when the consumer creates an exchange.",
"description": "Sets the exchange pattern when the consumer creates an exchange. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -299,7 +300,7 @@
},
"pollStrategy": {
"displayName": "Poll Strategy",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel.",
"description": "A pluggable org.apache.camel.PollingConsumerPollingStrategy allowing you to provide your custom implementation to control error handling usually occurred during the poll operation before an Exchange have been created and being routed in Camel. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,advanced",
"type": "object",
"kind": "parameter",
@ -314,7 +315,7 @@
},
"chatId": {
"displayName": "Chat Id",
"description": "The identifier of the chat that will receive the produced messages. Chat ids can be first obtained from incoming messages (eg. when a telegram user starts a conversation with a bot, its client sends automatically a \u0027/start\u0027 message containing the chat id). It is an optional parameter, as the chat id can be set dynamically for each outgoing message (using body or headers).",
"description": "The identifier of the chat that will receive the produced messages. Chat ids can be first obtained from incoming messages (eg. when a telegram user starts a conversation with a bot, its client sends automatically a \u0027/start\u0027 message containing the chat id). It is an optional parameter, as the chat id can be set dynamically for each outgoing message (using body or headers). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "producer",
"type": "string",
"kind": "parameter",
@ -331,7 +332,7 @@
},
"bufferSize": {
"displayName": "Buffer Size",
"description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client.",
"description": "The initial in-memory buffer size used when transferring data between Camel and AHC Client. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "number",
"kind": "parameter",
@ -347,7 +348,7 @@
},
"synchronous": {
"displayName": "Synchronous",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported).",
"description": "Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "advanced",
"type": "boolean",
"kind": "parameter",
@ -363,7 +364,7 @@
},
"proxyHost": {
"displayName": "Proxy Host",
"description": "HTTP proxy host which could be used when sending out the message.",
"description": "HTTP proxy host which could be used when sending out the message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "proxy",
"type": "string",
"kind": "parameter",
@ -380,7 +381,7 @@
},
"proxyPort": {
"displayName": "Proxy Port",
"description": "HTTP proxy port which could be used when sending out the message.",
"description": "HTTP proxy port which could be used when sending out the message. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "proxy",
"type": "number",
"kind": "parameter",
@ -397,7 +398,7 @@
},
"backoffErrorThreshold": {
"displayName": "Backoff Error Threshold",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent error polls (failed due some error) that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -412,7 +413,7 @@
},
"backoffIdleThreshold": {
"displayName": "Backoff Idle Threshold",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in.",
"description": "The number of subsequent idle polls that should happen before the backoffMultipler should kick-in. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -427,7 +428,7 @@
},
"backoffMultiplier": {
"displayName": "Backoff Multiplier",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured.",
"description": "To let the scheduled polling consumer backoff if there has been a number of subsequent idles/errors in a row. The multiplier is then the number of polls that will be skipped before the next actual attempt is happening again. When this option is in use then backoffIdleThreshold and/or backoffErrorThreshold must also be configured. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -442,7 +443,7 @@
},
"delay": {
"displayName": "Delay",
"description": "Milliseconds before the next poll.",
"description": "Milliseconds before the next poll. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -458,7 +459,7 @@
},
"greedy": {
"displayName": "Greedy",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages.",
"description": "If greedy is enabled, then the ScheduledPollConsumer will run immediately again, if the previous run polled 1 or more messages. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -474,7 +475,7 @@
},
"initialDelay": {
"displayName": "Initial Delay",
"description": "Milliseconds before the first poll starts.",
"description": "Milliseconds before the first poll starts. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -490,7 +491,7 @@
},
"repeatCount": {
"displayName": "Repeat Count",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever.",
"description": "Specifies a maximum limit of number of fires. So if you set it to 1, the scheduler will only fire once. If you set it to 5, it will only fire five times. A value of zero or negative means fire forever. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "number",
"kind": "parameter",
@ -506,7 +507,7 @@
},
"runLoggingLevel": {
"displayName": "Run Logging Level",
"description": "The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that.",
"description": "The consumer logs a start/complete log line when it polls. This option allows you to configure the logging level for that. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -533,7 +534,7 @@
},
"scheduledExecutorService": {
"displayName": "Scheduled Executor Service",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool.",
"description": "Allows for configuring a custom/shared thread pool to use for the consumer. By default each consumer has its own single threaded thread pool. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -548,7 +549,7 @@
},
"scheduler": {
"displayName": "Scheduler",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component",
"description": "To use a cron scheduler from either camel-spring or camel-quartz component For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "string",
"kind": "parameter",
@ -572,7 +573,7 @@
},
"schedulerProperties": {
"displayName": "Scheduler Properties",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler.",
"description": "To configure additional properties when using a custom scheduler or any of the Quartz, Spring based scheduler. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -589,7 +590,7 @@
},
"startScheduler": {
"displayName": "Start Scheduler",
"description": "Whether the scheduler should be auto started.",
"description": "Whether the scheduler should be auto started. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -605,7 +606,7 @@
},
"timeUnit": {
"displayName": "Time Unit",
"description": "Time unit for initialDelay and delay options.",
"description": "Time unit for initialDelay and delay options. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "object",
"kind": "parameter",
@ -633,7 +634,7 @@
},
"useFixedDelay": {
"displayName": "Use Fixed Delay",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details.",
"description": "Controls if fixed delay or fixed rate is used. See ScheduledExecutorService in JDK for details. For more details see <a target=\"_blank\" href=\"https://camel-docs.entaxy.ru/components/${camel-docs.version}/telegram-component.html\">Camel docs</a>",
"label": "consumer,scheduler",
"type": "boolean",
"kind": "parameter",
@ -1419,6 +1420,14 @@
}
}
]
},
"config": {
"configurable": true,
"fieldsConfigurableByDefault": true,
"configurableFields": {
"includeNames":["camel_baseUri","camel_authorizationToken"],
"includePatterns":[]
}
}
},
"path": {
@ -1521,4 +1530,4 @@
}
}
}
}
}

View File

@ -5,13 +5,13 @@
</bean>
<bean id="pooledConnectionFactory" class="org.messaginghub.pooled.jms.JmsPoolConnectionFactory" init-method="start" destroy-method="stop">
<property name="maxConnections" value="10"/>
<property name="maxSessionsPerConnection" value="100"/>
<property name="maxConnections" value="[=properties.maxConnections]"/>
<property name="maxSessionsPerConnection" value="[=properties.maxSessionsPerConnection]"/>
<property name="connectionFactory" ref="artemisConnectionFactory"/>
</bean>
<bean id="artemisConnectionFactory" class="org.apache.activemq.artemis.jms.client.ActiveMQJMSConnectionFactory">
<argument index="0" value="[=properties.connectionString]"/>
<argument index="1" value="[=properties.username!]"/>
<argument index="2" value="[=properties.password!]"/>
<argument index="1" value="[=properties.camel_username!]"/>
<argument index="2" value="[=properties.camel_password!]"/>
</bean>

View File

@ -1,5 +1,9 @@
[#ftl]
<bean id="[=objectId]" class="ru.entaxy.platform.runtime.connections.ftp.FtpConnectionComponent">
[=utils.createBeanProperties(properties, "camel_", true)]
<property name="connectionString" value="[=properties.connectionString]"/>
[#if properties.username??]<property name="username" value="[=properties.username]"/>[/#if]
[#if properties.password??]<property name="password" value="[=properties.password]"/>[/#if]
<property name="host" value="[=properties.host]"/>
[#if properties.port??]<property name="port" value="[=properties.port]"/>[/#if]
[#if properties.directoryName??]<property name="directoryName" value="[=properties.directoryName]"/>[/#if]
</bean>

View File

@ -1,10 +1,15 @@
[#ftl]
[#if properties.dataSourceName?has_content]
<reference id="dataSource" interface="javax.sql.DataSource" availability="mandatory"
filter="(osgi.jndi.service.name=[=properties.dataSourceName])"/>
[#else]
<bean id="dataSource" class="org.apache.commons.dbcp2.BasicDataSource">
<property name="url" value="[=properties.dataSourceUrl]"/>
<property name="driverClassName" value="[=properties.dataSourceClass]"/>
<property name="username" value="[=properties.dataSourceUsername!]"/>
<property name="password" value="[=properties.dataSourcePassword!]"/>
</bean>
[/#if]
<bean id="[=objectId]" class="org.apache.camel.component.jdbc.JdbcComponent">
[=utils.createBeanProperties(properties, "camel_", true)]

View File

@ -1,5 +1,9 @@
[#ftl]
<bean id="[=objectId]" class="ru.entaxy.platform.runtime.connections.sftp.SftpConnectionComponent">
[=utils.createBeanProperties(properties, "camel_", true)]
<property name="connectionString" value="[=properties.connectionString]"/>
[#if properties.username??]<property name="username" value="[=properties.username]"/>[/#if]
[#if properties.password??]<property name="password" value="[=properties.password]"/>[/#if]
<property name="host" value="[=properties.host]"/>
[#if properties.port??]<property name="port" value="[=properties.port]"/>[/#if]
[#if properties.directoryName??]<property name="directoryName" value="[=properties.directoryName]"/>[/#if]
</bean>