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 2007/06/18 13:08:25 UTC
[jira] Resolved: (AXIS2-2451) WS Policy Attachments for
services.xml
[ https://issues.apache.org/jira/browse/AXIS2-2451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Sanka Samaranayake resolved AXIS2-2451.
---------------------------------------
Resolution: Fixed
I am not convinced about the use of separate threads to resolve the policies that are refered by the <wsp:PolicyReference> elements because of the following reasons.
1) It is unnecessory to resolve any policy references that are in a policy object model unless we are performing any operations on it (e.g. normalize, merge).
2) There is a risk that the PolicyEngine will produce a policy model that contains references that would be resolved into actual policies in later point of time (via those resolving threads). It would complicate life if that happens where we've already started to process the policy model build partially.
H
> WS Policy Attachments for services.xml
> --------------------------------------
>
> Key: AXIS2-2451
> URL: https://issues.apache.org/jira/browse/AXIS2-2451
> Project: Axis 2.0 (Axis2)
> Issue Type: New Feature
> Reporter: Nencho Lupanov
> Assignee: Sanka Samaranayake
> Priority: Blocker
> Attachments: PolicyEngine.diff, PolicyReaderThread.java, PolicyReference.diff, PolicyReference.diff
>
>
> Axis2 does not recognize policy references in services.xml.
> Implementation should alow usage such:
> <wsp:PolicyReference
> URI="http://localhost:53307/policy.xml#UTOverTransport" />
> </wsp:PolicyAttachment>
--
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