By default the consumer will use the .ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored.

This can be used for automatic configuring JDBC data sources, JMS connection factories, AWS Clients, etc.Ĭ-error-handlerĪllows 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. This is used for automatic autowiring options (the option must be marked as autowired) by looking up in the registry to find if there is a single instance of matching type, which then gets configured on the component. With Windows or without an absolute localPath you may run into an exception like the following:Ĭaused by: : 'path': bad path: must start with '/': 'C:/My/File'Ĭaused by: : 'path': bad path: must start with '/': 'MyFile'Ĭ-enabled If the property is not set, the component will upload the file on a remote path equal to the local path. If this option has been configured then it takes precedence over uploading as a single file with content from the Camel message body (message body is converted into a byte array).įolder destination on Dropbox.

In case of 'force' if a file with the same name already exists on dropbox, this will be overwritten.įolder or file to upload on Dropbox from the local filesystem.

Add or force this option specifies how a file should be saved on dropbox: in case of 'add' the new file will be renamed if a file with the same name already exists on dropbox.

Dropbox transfer api