Project: mulestudio
Issue STUDIO-3181: DataSense support for properties placeholders
We need to define the experience of how to handle properties placeholder when using DataSense and Connectivity Testing. Work in progress... # *Properties files should be read from*: ** src/main/app ** $MULE_HOME/conf ** - this element can be global or a child element of {code} {code:xml} {code} # *UI* ** The table should list all the properties used in the Element Window, that can be use to retrieve metadata or test the connection. I don't think at the time being that there is a need to show properties used listed in another tabs or properties that are not used in these features ** For each item in the table we should display a list of the posible values retrieved from all the properties files. It would be good if we can also show, as in the mockup, the name of the file. ** If we are going to cache the values set by the user using the checkbox we need to define a way to clear the cache, or a way for the user to reconfigure this again. ** The combo should be also editable so that the user can manually write the values that he wants to set. # *Encrypted properties*, documentation [here| http://www.jasypt.org/encrypting-configuration.html] Example of a properties file using encrypted values: {code} datasource.driver=com.mysql.jdbc.Driver datasource.url=jdbc:mysql://localhost/reportsdb datasource.username=reportsUser datasource.password=ENC(G6N718UuyPE5bHyWKyuLQSm02auQPUtm) {code} Even if the value is shown as encrypted we should offer a way to the user to use DataSense and use the correct credentials to retrieve the Metadata. One simple way would be to make the table editable so that the user can manually write the pasword. *Acceptance criteria*: * Metadata and Connectivity testing should work using properties placeholders ${}, those properties files can be located in src/main/app in the $MULE_HOME\conf, if accesible, or the location can be manually specified in the xml using this tag .
Story points: 8