[Connector Docs] Suggestions for Improvements

[AmilaSamith]

Current Limitation

Suggestion 01

MI for VS Code provides the capability to copy JARs to the <PRODUCT_HOME>/lib folder while exporting the CApp. To do that we can copy the necessary JARs to the deployment > libs folder in the Explorer view.

It's better if we can instruct this approach in our connector docs without instructing to copy jars to <PRODUCT_HOME>/lib directly.

Suggestion 02

Currently some Inbound endpoint example documentations instruct developer to download and copy inbound endpoint jar to <PRODUCT_HOME>/lib. But with newest version of VS code extension those jars get downloaded and copied to deployment > libs. Then those jars will be exported with CApp.

So we need to remove that step from docs.

Eg: SMPP Inbound Endpoint Example

Suggestion 03

In creating inbound endpoints, with latest MI for VS code extension we can automatically generate injecting and error sequences. IMO we should clearly communicate that to developer the options he has through a Tip as bellow.

Eg: Tip in SMPP Inbound Endpoint Docs

Suggested Improvement

Improvement 01

Example Change.

---

1. Download jsmpp-2.1.0-RELEASE.jar and asyncretry-jdk7-0.0.6.jar and copy inside deployment > libs folder from Explorer view.

Version

4.3.0