You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Ivan (JIRA)" <ji...@apache.org> on 2011/05/08 16:00:03 UTC
[jira] [Created] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
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
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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ 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: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated AXIS2-5022:
------------------------
Attachment: AXIS2-5022.patch
Attach a draft patch, and it works in my local environment. Some of TCK cases related to it begun to pass. Not sure whether there are better ways ? Hope some dev members could help to give some comments. Thanks.
> 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033206#comment-13033206 ]
Andreas Veithen commented on AXIS2-5022:
----------------------------------------
Regarding item a., I think (but I'm not 100% sure) that Axis2 maps assertions to modules based on namespace URIs and doesn't consider the Java type of the assertion. Therefore one could probably implement this correctly even with the PrimitiveAssertion stuff.
> 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-01.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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Commented] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033661#comment-13033661 ]
Andreas Veithen commented on AXIS2-5022:
----------------------------------------
Regarding item b., I think that the MTOM module [1] is a good starting point to see how WS-Policy support could be added to the addressing module.
[1] modules/mtompolicy-mar/src/org/apache/axis2/mtompolicy/MTOMPolicy.java
> 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-01.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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated AXIS2-5022:
------------------------
Attachment: AXIS2-5022-01.patch
Fix a typo error in the last patch, I am still thinking how to implement it more gently based on Andreas' comments ...
> 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-01.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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Ivan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan updated AXIS2-5022:
------------------------
Attachment: (was: AXIS2-5022.patch)
> 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
>
>
> 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org
[jira] [Updated] (AXIS2-5022) Support addressing meta data with
policy 1.5 framework
Posted by "Andreas Veithen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-5022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen updated AXIS2-5022:
-----------------------------------
Affects Version/s: (was: 1.7.0)
1.6.0
Labels: Geronimo (was: )
> 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.6.0
> Reporter: Ivan
> Labels: Geronimo
> Fix For: 1.7.0
>
> Attachments: AXIS2-5022-01.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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org