Content Comparison

Editor Related Issue

• The below mentioned are the fields of AIS activities in which we are facing issues while implementing Config Management.
  Some activities already use different editors. When If we replace the editor with ConfigAwareTextEditor then it gives an impact on GUI as when config management is not enabled then we have to use another editor (ConfigAwareTextEditor) which will provide a “Use Config” checkbox on the UIalso the fields will not retain its older look on GUI.

Following are the activities with respective fields along with the screenshots of how they look on GUI.

1. JMS Provider uses InitialContextEditor as property editor for Additional Connection parameters field.
   

   Image Removed

   
   

   Image Added

   
   In case of using ConfigAwareTextEditor, it looks on GUI as
   

   Image Added

   
   

2. Database Info uses BshEditor as property editor for Kerberos Configuration field.
   

   Image RemovedImage Added

3. JMS Target uses CustomSchemaEditor as property editor for Message Properties field and TextEditor as property editor for Message Priorityand Time to Live fields.
   

   Image RemovedImage Added

   Image Removed

   
   
   

   Image Added

   Image Removed

   
   

   Image Added

   
   
   

4. JMS Source uses TextArea property editor for Time Out field.
   

   Image RemovedImage Added

   
   

5. FTP Source, Target, Event uses TextAreaEditor as property editor forAdd on Configuration field.
   

   Image Removed

   
   

   Image Added

   
   
   

• 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.