How to Control Binding Generation in Axis2 ?

Whenever you deploy a service in Axis2 , it generates a WSDL for you. You are able to see the WSDL generated when by executing a “?wsdl” for your service. If you look closer you will see that the WSDL generated has three bindings.

• SOAP11 binding
• SOAP12binding
• HTTPbinding

In addition to these bindings, there will be multiple port addresses for those bindings in the service section as well. Number of binding generation is independent of whether you use WSDL11 or WSDL2.0 .

In some instances, you do not need to generate all of those bindings and you may want to configure the types of binding Axis2 generates. Now let's see how we can do this with Axis2.

There are two ways of doing that, you can control that for all the services in the system, or, you can control that for a particular service only. If you want to control for all services then you need to add the following parameter(s) into axis2.xml, and alternatively, if you only want to control for a particular service then add the parameter(s) in services.xml

Disable SOAP11 binding – To disable SOAP11 binding, add the following parameter:

<parameter name=”disableSOAP11”>true</parameter>

Disable SOAP12 binding – To disable SOAP12 binding, add the following parameter

<parameter name=”disableSOAP12”>true</parameter>

Disable Http binding – To disable http binding, add the following parameter

<parameter name=”disableHTTP”>true</parameter>

With this approach you can configure the number of bindings you want to generate , but it is advisable to have at least one binding. .

Author

Deepal Jayasinghe is a Technical Lead at WSO2. Deepal at wso2 dot com