[
https://issues.apache.org/jira/browse/RAMPART-45?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12500332
]
Ruchith Udayanga Fernando commented on RAMPART-45:
--------------------------------------------------
IMHO Rampart should not save policy in any of these cases.
At the moment we only save policy at the service level and this can cause
problems in the case where we try to invoke different operations of the same
service. Therefore I suggest we simply remove saving policy.
Thoughts?
Thanks,
Ruchith
> Rampart always saving policy on ServiceContext properties/KEY_RAMPART_POLICY
> causes operation policy to be overwritten
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: RAMPART-45
> URL: https://issues.apache.org/jira/browse/RAMPART-45
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.2
> Reporter: Hans G Knudsen
> Attachments: policy_detection_save_key_rampart_policy.diff
>
>
> If Rampart detects a 'servicepolicy' and acting as initiator it always saves
> this policy on ServiceContext properties/KEY_RAMPART_POLICY.
> This causes 'EffectivePolicy' to be overwritten if eg running RM.
> Example of setting service policy + operation policy
> //
> AxisService axisService =
> serviceClient.getServiceContext().getAxisService();
>
> axisService.getPolicyInclude().setPolicy( servicePolicy );
>
> AxisOperation operation =
> axisService.getOperation(ServiceClient.ANON_OUT_IN_OP);
> operation.getPolicyInclude().setPolicy( operationPolicy );
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
