Key Concern related to Config Management Implementation

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. If we replace the editor with ConfigAwareTextEditor then it gives an impact on GUI as when config management is not enabled then also 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.
   
   

   Open

   

   
   In case of using ConfigAwareTextEditor, it looks on GUI as
   
   

   Open

   

   
   
   

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

    

    

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

   
   
   
   

   
   
   

   
   
   
   

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

   
   
   

5. FTP Source, Target, Event uses TextAreaEditor as property editor for Add 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.