[
https://issues.apache.org/jira/browse/AXIS2-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580404#action_12580404
]
Jeff Barrett commented on AXIS2-3626:
-------------------------------------
Dims and I just discussed this on the phone. The function added under
Axis2-3568 does not duplicate the code in these classes. Specifically, that
Jira added the ability for JAXWS Handlers associated with an endpoint to
participate in mustUnderstand processing. The purpose of the other classes is:
a) MustUnderstandValidationDispatcher checks for a very specific conformance
requirement in the JAXWS 2.0 TCK that states that an operation that can not be
resolved and that includes unprocessed mustUnderstand headers must get
mustUnderstand fault, not an operation not found fault.
b) SoapMessageMUProviderChecker is actually part of a test, so should be
ignored for this Jira.
c) MustUnderstandChecker: This marks any headers corresponding to paramaters on
the SEI as understood.
So, (a) and (c) don't duplicate any new code. While the logic could be moved
to the JAXWS Message Receiver alongside the new code for Axis2-3568, I don't
think we should do that. The reason is that (a) and (c) are processing
mustUnderstand headers in the dispatch chain, which is the prefered way of
doing that. The code added to allow the JAXWS application handlers to be
involved in mustUnderstand processing had to be done in the MessageReceiver
because the handlers could only be invoked (to get the list of headers they
understand) after the container breech since the handlers must run under the
application context.
> Remove MustUnderstandValidationDispatcher / SoapMessageMUProviderChecker /
> MustUnderstandChecker
> ------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3626
> URL: https://issues.apache.org/jira/browse/AXIS2-3626
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Davanum Srinivas
> Assignee: Jeff Barrett
> Priority: Critical
> Fix For: 1.4
>
>
> Now that we added the hook for JAXWS to participate in mu handling, do we
> need these classes anymore?
> org.apache.axis2.jaxws.dispatchers.MustUnderstandValidationDispatcher
> org.apache.axis2.jaxws.provider.SoapMessageMUProviderChecker
> org.apache.axis2.jaxws.dispatchers.MustUnderstandChecker
> thanks,
> dims
--
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]
