Hello! My first posting on this list, please be gentle 😊 We’ve been using Apache Camel for a short while, and now we have started to use Quartz as the scheduler for SFTP transfers. We have two nodes, and we've decided on the use of Quartz for clustering.
To simplify for our developers and integrators to set up new SFTP transfers (and migrate from other platform), we have an SFTP routebuilder that sets the common URL parameters that fits our environment and usage, to keep the noise/clutter down as much as possible in the properties files. All parameters are added using the Camel's URISupport library, which URL-encodes the parameters. Thus, it also encodes the quartz-related parameters -- the cron string and time zone ID, which the QuartzScheduledPollConsumerScheduler can't decode (it merely replaces '+' with space in the cron string). It seems to be the same in all 3.x versions, and in master. I did some experiments locally with 3.14.8 and came up with a few simple changes in QuartzScheduledPollConsumerScheduler which solves my problem, and I think it is a general solution. How would you suggest I continue? Should I make a jira ticket before I push my changes in my fork? I guess I can't just create my own branch in the main repo. Peter
