Asanka Abeyweera

## Feature Request: WSO2 Integration Studio currently generates a multi-maven module project containing integration artifacts. In Choreo, we create a component from this multi-maven module project, which subsequently generates one...

## Feature Request: We have recently introduced a non-server mode for the WSO2 Micro Integrator (MI), which allows users to run it similar to how one would run a main...

Currently we copy sql resources to features/org.wso2.carbon.business.messaging.core.feature/src/main/resources when building. Better to keep the files at target location or use target directory for resource copying

modules should be restructured to allow extensions

1

I propose the following module restructuring to manage multiple coordination strategy implementations effectively. List of modules, * **org.wso2.carbon.cluster.coordinator.core** - This will include the core logic independent of the coordination strategy...

Data cleaning will be easier if we reuse the same node ID for nodes. We can persist in $CARBON_HOME similar to how the pid is persisted

Currently, It is only possible to get the node details of the leader node. Maybe we can return the node ID when joining the cluster group and use that to...

Database Scripts for the following DBs should be added, * MSSQL * MySQL * Oracle * Oracle RAC * PostgreSQL

This should be done to avoid two coordinators operation in the same cluster group. Refer the following commit for similar implementation: https://github.com/wso2/andes/commit/cef1d6a7c21b4202b3b51c51d0b1ca14766a2baf

Absolute method reference: org.wso2.carbon.cluster.coordinator.rdbms.RDBMSCommunicationBusContextImpl#clearMembershipEvents(java.lang.String, java.lang.String)