[
https://issues.apache.org/jira/browse/AXIS2-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Davanum Srinivas resolved AXIS2-3523.
-------------------------------------
Resolution: Fixed
> Proper usage of binding hierarchy
> ---------------------------------
>
> Key: AXIS2-3523
> URL: https://issues.apache.org/jira/browse/AXIS2-3523
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Sanka Samaranayake
> Assignee: Sanka Samaranayake
> Attachments: ProperUsageOfBindingHierarchy.patch
>
>
> 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 three 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
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
