cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CXF-1409) Endpoint polices referenced from WSPolicyFeature can not be applied if EndpointPolicy already exists
Date Wed, 30 Jan 2008 21:51:35 GMT

     [ 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.patch

1. EndpointPolicy and PolicyEngine has been changed to better deal with updating EndpointPolicies

2. WSPolicyFeature does not add duplicate Policy Extensors but rather adds them to a givem
EndpointPolicy

3. Various tests updated and added

This is not the final change in this area


> 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.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.


Mime
View raw message