Editor Related Issue
...
JMS Provider uses InitialContextEditor as property editor for Additional Connection parameters field.
Database Info uses BshEditor as property editor for Kerberos Configuration field.
JMS Target uses CustomSchemaEditor as property editor for Message Properties field and TextEditor as property editor for Message Priorityand Time to Live fields.
JMS Source uses TextArea property editor for Time Out field.
FTP Source, Target, Event uses TextAreaEditor as property editor forAdd on Configuration field.
Fields like Additional Connection parameters and Message Properties stores data in xml form in the database which is a challenge to parse the xml when we use "use config" and give data in config form (${Config:}).
Field like Port takes integer as input on GUI.