Hi, Axis2 has a set of description classes (i.e. AxisEndpoint, AxisBinding .. etc) but it doesn't use them properly in the deployment time or in runtime. For instance when a service is deployed without a WSDL, the resulting AxisService doesn't contain any binding hierarchy. But when you generate a WSDL via AxisService2WSDL11 you will see three bindings automatically generated. I believe that the proper way of doing this is to create binding hierarchies representing those default bindings at the time of deployment (in this case via ServiceBuilder) and serialize those binding hierarchies directly in AxisService2WSDL11. It would provide a cleaner way of attaching policies to a service. For example Rampart policies are meaningful only at binding level. Hence we should attach them only to SOAP bindings and maintenance of proper binding hierarchy in a service description would provide a cleaner way of doing that. This would also allow to enhance ServiceBuilder to process external policy attachments via services.xml
I've created a JIRA issue[1] for this and uploaded a patch. I will commit it in few days if no one objects. Thanks, Sanka [1] https://issues.apache.org/jira/browse/AXIS2-3523 -- Sanka Samaranayake WSO2 Inc. http://sankas.blogspot.com/ http://www.wso2.org/
