[
https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13030570#comment-13030570
]
Ivan commented on AXIS2-5022:
-----------------------------
Before creating the patch, I checked those sub modules in current Axis2, e.g.
mtompolicy, and also considered to do some changes in addressing module, but
turn to the current solution due to
a. It looks to me that the default PolicyContainingPrimitiveAssertion and
PrimitiveAssertion are enough for describe the addressing meta data, also the
default builder from neethi is OK. I am thinking that, only extra attributes
exist in the meta data or the policy configuration is too complex, then some
new assertions and builders are required. Please correct me, as I am not
familiar with this part :-)
b. Yes, configuring those policy configurations in the addressing module is
more nature. In the Axis2 kernel module, I saw a class named
WSDLBasedPolicyProcessor, it seems to be used to engage the required modules,
but I did not find any codes using it, I missed anything ? So, I thought that I
have to manually engaged the addressing modules in the
configurationAddressingPolicyFromWSDL, and actually I refer to some similar
codes in both client and server addressing configurator
c. I found one comment in the axis2-jawx/o.a.axis2.jaxws.BindingProvider, there
are some comments on line 100, seems that I have to configure the addressing
properties from WSDL once the EndpointDescription info object.
--->
// Addressing is disabled by default unless it is turned on in the WSDL
String addressingFlagFromWSDL =
AddressingHelper.getAddressingRequirementParemeterValue(endpointDesc.getAxisService());
if(AddressingConstants.ADDRESSING_UNSPECIFIED.equals(addressingFlagFromWSDL)){
requestContext.put(AddressingConstants.DISABLE_ADDRESSING_FOR_OUT_MESSAGES,
Boolean.TRUE);
}
<---
Thanks, Andreas.
> 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: [email protected]
For additional commands, e-mail: [email protected]
