this one helps. In the end the main problem showed up to be in proper MessageBuilder configuration. As long as the service response was a simple XML and as such it was marked in the response header, WSO2 passed it to the client just fine. Once the response was marked differently - in my case it was application/atom+xml, the default MessageBuilder did not applied and thus WSO2 expected the contnent to be SOAP. I added a builder configuration to the \repository\conf\axis2\axis2.xml:
I wish did fix the issue. If you're providing the UI for your service in the Carbon admin console itself, which probably means you're extending/enhancing product functionality then yes, you must go down the path of writing OSGi bundles. Example: you're adding a new throttling algorithm which allow users to configure new throttling policies through the admin console which accepts many different parameters. If you're developing functionality which will be used in a user level application, then you're not suppose to go down the OSGi path. Unless you're enhancing/modifying the platform you don't have to know anything about OSGi. For end users, when configuring the ESB, you don't have to write custom code unless your scenario cannot be configured with the existing mediators. ESB and DSS therefore follows a configuration driven approach (for end users) when you have to develop new services.
How to Secure REST Service using OAuth2 with WSO2 ESB 4.9.0 & WSO2-IS 4.5.0
Hope this helps Well. Until now there is no way to do this. The only workaround i can fin was to avoid using SAML by configuring the same user and tenant database used by the SSO provider to be used by the WSO2 product.
WSO2 IS 5.2.0 Admin SOAP Services response time compared to WSO2 IS 5.0.0