[
https://issues.apache.org/jira/browse/CXF-1409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Beryozkin updated CXF-1409:
----------------------------------
Attachment: cxf-patch-1409-v2.patch
The previous attachment had some left-overs from other patches.
Summary :
1. PolicyEngine has separate maps now for keeping client and server endpoint
policies as the assumption that they're the same (in midtier) is not safe
2. EndpointPolicy has an explicit updatePolicy methods for various providers be
able to contribute to existing policy (dynamically)
3. WSPolicyFeature does not add Policy instances as extensors to EndpointInfo
which are duplicated anyway in the EndpointPolicy
4. Some initial workaround around Neethi'lack for proper normalization support
in EndpointPolicy
> Endpoint polices referenced from WSPolicyFeature can not be applied if
> EndpointPolicy already exists
> ----------------------------------------------------------------------------------------------------
>
> Key: CXF-1409
> URL: https://issues.apache.org/jira/browse/CXF-1409
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.1
> Reporter: Sergey Beryozkin
> Fix For: 2.1
>
> Attachments: cxf-patch-1409-v2.patch
>
>
> If a jaxws:endpoint is using WSPolicyFeature to refer to WS-Policy
> expressions and a corresponding EndpointPolicy already exists then these
> polices will have no effect.
> This can happen if a policy engine has been explicitly enabled or if at least
> 2 jaxws:endpoints are using WSPolicyFeature.
> In the former case, AbstractHttpDestination will cause a somewhat premature
> EndpointPolicy creation, while in the latter case
> WSPolicyFeature will explicitly enable policy engine which in turn cause an
> AbstractHttpDestination for the second endpoint to (early) create
> EndpointPolicy.
> As a result, after WSPolicyFeature adds Policy extensors to EndpointInfo,
> these extensors are never checked again to sync up them with already existing
> EndpointPolicy.
> While the way AbstractHttpDestination creates EndpointPolicy needs to be
> reviewed, the actual problem is that it's not possible to update
> EndpointPolicy after it's been created
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
