You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Sanka Samaranayake (JIRA)" <ji...@apache.org> on 2008/02/20 11:48:43 UTC
[jira] Created: (AXIS2-3523) Proper usage of binding hierarchy
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
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3523) Proper usage of binding hierarchy
Posted by "Keith Godwin Chapman (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571017#action_12571017 ]
Keith Godwin Chapman commented on AXIS2-3523:
---------------------------------------------
Sanka we have these checks in WSDL genaration, Hence I beleive should take these two parameters into account when creating the binding hierarchy. i.e depending on these drop the genaration on bindings for SOAP 1.1 and HTTP.
boolean disableREST = false;
Parameter disableRESTParameter =
axisService.getParameter(Constants.Configuration.DISABLE_REST);
if (disableRESTParameter != null &&
JavaUtils.isTrueExplicitly(disableRESTParameter.getValue())) {
disableREST = true;
}
// axis2.xml indicated no SOAP 1.2 binding?
boolean disableSOAP12 = false;
Parameter disableSOAP12Parameter =
axisService.getParameter(org.apache.axis2.Constants.Configuration.DISABLE_SOAP12);
if (disableSOAP12Parameter != null &&
JavaUtils.isTrueExplicitly(disableSOAP12Parameter.getValue())) {
disableSOAP12 = true;
}
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Updated: (AXIS2-3523) Proper usage of binding hierarchy
Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanka Samaranayake updated AXIS2-3523:
--------------------------------------
Attachment: ProperUsageOfBindingHierarchy.patch
I propose the following patch to fixes some of those issues mentioned. I will commit it in few days if no one objects.
Thanks,
Sanka
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Assigned: (AXIS2-3523) Proper usage of binding hierarchy
Posted by "Sanka Samaranayake (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanka Samaranayake reassigned AXIS2-3523:
-----------------------------------------
Assignee: Sanka Samaranayake
> 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
>
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-3523) Proper usage of binding hierarchy
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-3523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12576676#action_12576676 ]
Davanum Srinivas commented on AXIS2-3523:
-----------------------------------------
looks like this is fixed now - http://svn.apache.org/viewvc?rev=633485&view=rev
> 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-3523) Proper usage of binding hierarchy
Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
[ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org