Łukasz Dywicki created SWITCHYARD-759: ----------------------------------------- Summary: Reflect Camel endpoint hierarchy in Switchyard configuration binding Key: SWITCHYARD-759 URL: https://issues.jboss.org/browse/SWITCHYARD-759 Project: SwitchYard Issue Type: Sub-task Components: component-camel Reporter: Łukasz Dywicki Assignee: Łukasz Dywicki Components already implemented in Switchyard do not follow class hierarchy from Camel. For example atom endpoint is schedule based, just like file/ftp/sftp and so on. They have following properties in common (bolder will be supported): * *startScheduler* * *initialDelay* * *delay* * *timeUnit* * *useFixedDelay* * *pollStrategy* * runLoggingLevel * sendEmptyMessageWhenIdle File and Ftp have following in common (bolder will be supported): * *localWorkDirectory* * *autoCreate* * startingDirectoryMustExist * *directoryMustExist* * *bufferSize* * fileExist * *noop* * *recursive* * *delete* * *flatten* * *maxMessagesPerPoll* * eagerMaxMessagesPerPoll * *maxDepth* * *minDepth* * tempPrefix * tempFileName * eagerDeleteTargetFile * *include* * *exclude* * *charset* * *fileName* * *move* * *moveFailed* * *preMove* * *idempotent* * *idempotentRepository* * *filter* * *antFilter* * sorter * sortBy * readLock * readLockCheckInterval * readLockTimeout * exclusiveReadLockStrategy * *keepLastModified* * doneFileName -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira