[
https://issues.apache.org/jira/browse/CXF-4547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13472075#comment-13472075
]
Jason Pell edited comment on CXF-4547 at 10/9/12 4:37 AM:
----------------------------------------------------------
Updated patch which uses the external policy ws-policy namespace for the policy
reference instead of a hard coded namespace that might be different.
Updated the test case to test this scenario.
This patch is now considered complete awaiting review and hopefully inclusion
into 2.7.1 / 2.6.4
was (Author: pellcorp):
Updated patch which uses the external policy ws-securitypolicy namespace
for the policy reference instead of a hard coded namespace that might be
different.
Updated the test case to test this scenario.
This patch is now considered complete awaiting review and hopefully inclusion
into 2.7.1 / 2.6.4
> java first externalAttachment wsdl enhancements
> -----------------------------------------------
>
> Key: CXF-4547
> URL: https://issues.apache.org/jira/browse/CXF-4547
> Project: CXF
> Issue Type: Bug
> Components: WS-* Components
> Affects Versions: 2.6.2, 2.6.3, 2.7.0
> Reporter: Jason Pell
> Attachments: patch.txt
>
>
> When I define a <p:externalAttachment
> location="classpath:SslWithUsernamePasswordToken.xml"/>
> I expect to see the associated Policies directly underneath the
> wsdl:definitions, just like how PolicyAnnotationListener does it.
> i would also expect the generated wsdl to correctly reflect if I am
> associating a policy with just a message rather than an operation as a whole.
>
--
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
