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

[Improvement]: (Usability) DSS namespace and Synapse namespace added automatically #3646

Open
Bhashinee opened this issue Sep 30, 2024 · 0 comments

Comments

@Bhashinee
Copy link
Member

Bhashinee commented Sep 30, 2024

Describe your problem(s)

When doing transformations we noticed

  1. Whenever a DSS response is there, DSS namespace is added automatically. Issue here is integration developer does not know that such a thing is added until he test it up. If we have a portal for testing DSS operations inside Integration Studio itself, this could be resolved to a certain extent. However, cannot we get rid of DSS namespace? Otherwise, in the response to the caller this namespace will be there or the following transformations will fail as this namespace is not there.
image
  1. In the same way synapse namespace is also added. We need to specifically remove this namespace using Payload Factory mediator. Cannot we make the default behaviour not to add the synapse namespace? This also, the integration developer will notice in the runtime - that an undesired namespace is added.

Describe your solution(s)

  1. However, cannot we get rid of DSS namespace? Otherwise, in the response to the caller this namespace will be there or the following transformations will fail as this namespace is not there.

  2. Cannot we make the default behaviour not to add the synapse namespace? This also, the integration developer will notice in the runtime - that an undesired namespace is added.

Product : WSO2MI 4.2.0
Update level : 56
Opened by : [email protected]

Related issue(s) (optional)

https://github.com/wso2-enterprise/wso2-mi-internal/issues/668

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