[New Feature]: Expand third party connectors

[chathuranga-jayanath-99]

Description

This feature involves implementing new connectors for key communication protocols. The identified connectors to be implemented are as follows:

• HTTP
• JMS
• MQTT
• WebSocket
• AMQP
• HL7

Describe your problem(s)

No response

Describe your solution(s)

No response

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

[chathuranga-jayanath-99]

Based on our initial discussion, we will begin by implementing the HTTP connector. In this phase, the connector will support a single operation for sending requests.

• Connection Creation: The URL path will be retrieved during the connection setup.
• Request Execution: The following parameters will be collected when sending a request: HTTP method type, headers, path parameters, query parameters, and the request body.

[chathuranga-jayanath-99]

The connection initiation and request sending operations have been implemented with the following features.

The connection is established using the following:

• url

In the send request operation, the following inputs are taken:

• method - can be: get, post, put, patch, delete, head, options
• headers - a comma separated list (h1: v1, h2:v2)
• path parameters - a comma separated list (p1: v1, p2:v2)
• query parameters - a comma separated list (q1: v1, q2:v2)
• request body type - can be: json/xml/text
• request body
• properties
  • POST_TO_URI
  • FORCE_SC_ACCEPTED
  • DISABLE_CHUNKING etc

Note: Currently, headers, path parameters, and query parameters accept a comma-separated list. However, once the feature from Issue #413 is available, we plan to switch to using that feature to handle these lists.