Enterprises are inherently complex, comprising of hundreds of applications with completely different semantics. Some of these applications are custom built, where as some are acquired from third parties and some even can be a combination of both and they can be operating in different system environments.
WSO2 VMware Images helps you to try our products inside your virtualized environments without having to go through the trouble of installation and configuration. Download an image and get your hands on cutting edge, lightweight SOA middleware right away!
WSO2 Governance Registry is a product from WSO2 that facilitates you to govern the SOA platform of your organization by helping you store and manage SOA meta data. The product is free and open source with Apache licence and you can download it from http://wso2.org/projects/governance-registry
Post to twitter
Hi You have to disengage the
Hi
You have to disengage the addressing module from the proxy. There is a configuration tag called 'enableAddressing' in the proxy configuration [1] and if it is present, then we explicitly engage the addressing module. However, as by default in ESB , the addressing module globally is enable(look at axis2.xml), implicitly it engages to every service even the 'enableAddressing' has not been specified.
This is observable if you run the sample 150 and go to the URL [2]. {Global level - addressing-1.6-wso2v1}
So you have to disable addressing module globally(you have to test properly this as we always use addressing) and add 'enableAddressing' as needed to the services require addressing.
Thanks
Indika
[1]https://svn.apache.org/repos/asf/synapse/trunk/java/modules/core/src/main/java/org/apache/synapse/config/xml/ProxyServiceFactory.java
[2]https://localhost:9443/carbon/modulemgt/service_modules.jsp?serviceName=StockQuoteProxy