Hi All, ESB tooling requires adding of required dependencies such as *".jars" *to *"ESB/lib" *directory, where the user has to search for the relevant jar & download it, copy it to the lib directory. Due to some license constrains we can't ship & redistribute those 3rd party jars with the developer studio.
In order to improve the developer experience, we are planning to embed new feature to download the relevant .jars using maven. The steps are as follows 1. The user has to select the relevant database driver (eg: mysql , mssql). 2. The user can select a version from a list of supported versions provided to the user. 3. A download button is provided to download the driver. 4. Once the download button is clicked the relevant dependency is added to the pom.xml file and it is built. 5. The relevant dependencies are downloaded and copied to the *"ESB/lib"* directory. 6. A test connection button is provided so that the user can check the connectivity to the relevant database. When deploying the *"CApp" *to development environment the dependent .jars would be compressed as a zip file and the user would be notified, that he has to copy the created zip file and extract it to the lib directory of the *"ESB/lib"*. If users trying out the scenario inside the EI Tooling, all relevant jars will automatically copy to Micro Integrator & run accordingly. The same approach could be extended to configure ESB's JMS transport, to download required dependent *".jars"* to the *"ESB/lib"* directory. (eg : configuring ActiveMQ, JBossMQ). Sample view of the download window is given below. [image: Screenshot from 2019-02-11 16-45-07.png] Thanks, -- *Sangeeth Karunaratne* Software Engineering Intern | WSO2 Inc. Email: sange...@wso2.com Mobile: +94767031534 Web: http://wso2.com
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
