[
https://issues.apache.org/jira/browse/CXF-4532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467496#comment-13467496
]
Jason Pell commented on CXF-4532:
---------------------------------
If I actually use two different policies (two different files with different
policy names) then both policies are applied at the operation level. I should
be able to use the same policy for two different operations. I figure its
probably the PolicyAnnotationListener that I need to look at.
> Java First Policy buggy
> -----------------------
>
> Key: CXF-4532
> URL: https://issues.apache.org/jira/browse/CXF-4532
> Project: CXF
> Issue Type: Bug
> Components: JAX-WS Runtime, WS-* Components
> Affects Versions: 2.6.2
> Reporter: Jason Pell
> Labels: patch
> Fix For: 2.6.3, 2.7.0
>
> Attachments: PolicySample.tar.gz
>
>
> http://mail-archives.apache.org/mod_mbox/cxf-users/201206.mbox/%3c1340804477741-5710372.p...@n5.nabble.com%3E
> Ok so this problem is actually wider ranging in the java first @Policy stuff
> than I expected.
> So here are the problems so far:
> 1) If I define an external PolicyReference in jaxws:endpoint it is not
> included in the WSDL but is validated.
> 2) If I define an inline PolicyReference same problem as for 1.
> 3) If I use SEI and reference the same policy file twice at the operation
> level its ignored for all but the last reference.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
