Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Task]: Task to do when upgrading synapse-core #3522

Open
anupama-pathirage opened this issue Aug 16, 2024 · 0 comments
Open

[Task]: Task to do when upgrading synapse-core #3522

anupama-pathirage opened this issue Aug 16, 2024 · 0 comments

Comments

@anupama-pathirage
Copy link
Contributor

Description

Moving the issue from https://github.com/wso2-extensions/esb-inbound-dbevent/issues/25

image

Description:
To fix the issue [2] in the EI 6.5.0 product, the property "inbound.endpoint.name" needs to be set to message context.
EI 6.5.0 packs synapse-core v2.1.7.wso2v111 and this property is defined in that synapse version. However the master branch of this repo currently depends on synapse-core v2.1.3-wso2v5 and this constant is not defined in this synapse version.
Therefore the constant is hard coded in this repo itself in [1].

Since defining the constant here might break things in future (in case the property name changes in future in the synapse-core), I have created this issue.

When upgrading the synapse-core dependency in this repo, please remove this constant definition in [1], and use the constant imported from synapse wherever it is used in this repo.

[1] https://github.com/wso2-extensions/esb-inbound-dbevent/blob/master/src/main/java/org/wso2/carbon/inbound/poll/dbeventlistener/DBEventConstants.java#L35
[2] wso2/product-ei#5527

Affected Product Version:
N/A
OS, DB, other environment details and versions:
N/A
Steps to reproduce:
N/A

Related Issues:
wso2/product-ei#5527

Describe your task(s)

No response

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant