[
https://issues.apache.org/jira/browse/AXIS2-5348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13398313#comment-13398313
]
Sagara Gunathunga commented on AXIS2-5348:
-------------------------------------------
First, Axis2 WS-Policy guide[1] mention that Axis2 fully supports for WS Policy
at client-side including capability to engage the required modules. At the
moment this is possible for some of the modules such as security but not for
Addressing. If someone want to enforce WS-Addressing on messages above
statement should support for that too. IMHO is due to usefulness of this
feature we should support for Addressing Meta data. Also this is necessary
feature to fully support JAX-WS spec.
With committed changes it is possible to support basic use of WSAM ( i.e -
engage Addressing module and add headers). What I believe is next step would be
to add WSAM processing through Neethi to Addressing module, keeping these
issues as it is ( I mean without supporting to above use case) won't help for
anyone.
[1] - http://axis.apache.org/axis2/java/core/docs/WS_policy.html
> Addressing Module should have supported-policy-namespaces
> ----------------------------------------------------------
>
> Key: AXIS2-5348
> URL: https://issues.apache.org/jira/browse/AXIS2-5348
> Project: Axis2
> Issue Type: Bug
> Components: Addressing
> Affects Versions: 1.5.6, 1.6.2
> Reporter: Sagara Gunathunga
> Assignee: Sagara Gunathunga
> Fix For: 1.5.7, 1.7.0, 1.6.3
>
>
> Addressing module.xml file does not contains supported-policy-namespaces
> entry this results into not properly engaging Addressing module for client
> stub generated from a Policy aware ( Addressing meta data polices) WSDL file.
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
