[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030516#comment-13030516
]
Andreas Veithen commented on AXIS2-5022:
----------------------------------------
By design, Axis2 is able to engage modules automatically based on policies
present in the WSDL. The configureAddressingPolicyFromWSDL method bypasses (and
duplicates) this mechanism and in addition only works for JAX-WS. The correct
way to implement this is to create Neethi assertion builders and modify the
addressing module so that it is able to process these assertions and to
configure the service according to the information found in the assertions.
> Support addressing meta data with policy 1.5 framework
> ------------------------------------------------------
>
> Key: AXIS2-5022
> URL: https://issues.apache.org/jira/browse/AXIS2-5022
> Project: Axis2
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.7.0
> Reporter: Ivan
> Fix For: 1.7.0
>
> Attachments: AXIS2-5022.patch
>
>
> Since the trunk has been upgraded to use neethi 3.0.0, those addressing
> metadata should be supported. Actually, in the JAX-WS TCK cases, many cases
> use it for declaring addressing requirement.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
