You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "S.Uthaiyashankar (JIRA)" <ji...@apache.org> on 2008/06/25 11:34:45 UTC
[jira] Created: (AXIS2C-1201) When same operation is defined in
Service level as well as module level, service level operation should be
used.
When same operation is defined in Service level as well as module level, service level operation should be used.
----------------------------------------------------------------------------------------------------------------
Key: AXIS2C-1201
URL: https://issues.apache.org/jira/browse/AXIS2C-1201
Project: Axis2-C
Issue Type: Improvement
Components: core/deployment
Affects Versions: Current (Nightly)
Reporter: S.Uthaiyashankar
Assignee: S.Uthaiyashankar
Fix For: Current (Nightly)
Module operations will be added to the services for which the module is engaged. Since module operations are global for all the services engaging it, it is natural to overwrite operation settings in service.xml. For example, if security policy is given in module level operation and if a particular service wants to give a different policy to that operation, we should be able to define same operation in service.xml with different security policy. In such cases, policy defined in service.xml should be used.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Commented: (AXIS2C-1201) When same operation is defined in
Service level as well as module level, service level operation should be
used.
Posted by "Damitha Kumarage (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608322#action_12608322 ]
Damitha Kumarage commented on AXIS2C-1201:
------------------------------------------
Module is a way of extention to the Axis2/C core functionality. Service writer utilize functionlity provdided by Axis2/C core + mdules. So it is natural for him to expect the ability to override the functionlity provided by core+modules. So +1 from me.
> When same operation is defined in Service level as well as module level, service level operation should be used.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1201
> URL: https://issues.apache.org/jira/browse/AXIS2C-1201
> Project: Axis2-C
> Issue Type: Improvement
> Components: core/deployment
> Affects Versions: Current (Nightly)
> Reporter: S.Uthaiyashankar
> Assignee: S.Uthaiyashankar
> Fix For: 1.4.1
>
>
> Module operations will be added to the services for which the module is engaged. Since module operations are global for all the services engaging it, it is natural to overwrite operation settings in service.xml. For example, if security policy is given in module level operation and if a particular service wants to give a different policy to that operation, we should be able to define same operation in service.xml with different security policy. In such cases, policy defined in service.xml should be used.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
[jira] Resolved: (AXIS2C-1201) When same operation is defined in
Service level as well as module level, service level operation should be
used.
Posted by "S.Uthaiyashankar (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2C-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
S.Uthaiyashankar resolved AXIS2C-1201.
--------------------------------------
Resolution: Fixed
Fix Version/s: (was: Current (Nightly))
1.4.1
Implemented in revision 671486
> When same operation is defined in Service level as well as module level, service level operation should be used.
> ----------------------------------------------------------------------------------------------------------------
>
> Key: AXIS2C-1201
> URL: https://issues.apache.org/jira/browse/AXIS2C-1201
> Project: Axis2-C
> Issue Type: Improvement
> Components: core/deployment
> Affects Versions: Current (Nightly)
> Reporter: S.Uthaiyashankar
> Assignee: S.Uthaiyashankar
> Fix For: 1.4.1
>
>
> Module operations will be added to the services for which the module is engaged. Since module operations are global for all the services engaging it, it is natural to overwrite operation settings in service.xml. For example, if security policy is given in module level operation and if a particular service wants to give a different policy to that operation, we should be able to define same operation in service.xml with different security policy. In such cases, policy defined in service.xml should be used.
--
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-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org