[
https://issues.apache.org/jira/browse/AXIS2-2853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12509989
]
Jeff Barrett commented on AXIS2-2853:
-------------------------------------
I have backed out the changes made (under revision 549924) which introduced the
API. This rollback was commited in revision 552954.
Note that this does not fix this Jira; it simply removes the API changes for
RC1. Fixing this Jira as discussed on the list will be done as follows:
I think for 1.3, the JAXWS handler hack will work. Here's my proposal for
1.3 which removes the new API from AxisOperation added in revision 549924
and has a minimal effect on the JAXWS code that is doing the
mustUnderstand validation for SEI header parameters:
1) In modules/kernel, remove the following methods from AxisOperation:
registerUnderstoodHeaderQNames(QName) and getUnderstoodHeaderQNames().
This removes the new API that Sanjiva was concerned about. (Done in revision
552954)
2) In modules/metadata, change OperationDesc from using the above
AxisOperation methods to instead set a property on the AxisOperation to
contain the QNames for header parameters.
3) In modules/jaxws, add a new JAXWS handler which will look on the
AxisOperation for the property set in (2) and if found it will mark any
headers with the associated QNames as processed.
4) In modules/kernel AxisEngine, remove the understood-header-processing
logic from checkMustUnderstand and change it back to simply checking for
any headers that are marked mustUnderstand bur are not marked processed.
(Done in revision 552954)
I will not update axis2.xml to include the handler in (3); that can be
done systems that are integrating Axis2 and JAXWS (such as Geronimo).
For post-1.3, I have a proposal for extensible, pluggable
mustUnderstand-header-validation that solves all the problems we were
discussing, including allowing higher level components to participate in
mustUnderstand checking. I will be sending out that post 1.3 proposal
later on.
> Pluggable Must Understand Handling?
> -----------------------------------
>
> Key: AXIS2-2853
> URL: https://issues.apache.org/jira/browse/AXIS2-2853
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Reporter: Davanum Srinivas
> Assignee: Jeff Barrett
> Priority: Blocker
> Fix For: 1.3
>
>
> Discussion here - http://marc.info/?t=118266801700001&r=1&w=2
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
