You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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)
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.
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]
Describe your problem(s)
When doing transformations we noticed
Describe your solution(s)
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.
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
The text was updated successfully, but these errors were encountered: