I would like to propose a change to handle certain situations in jaxws
where we need to postpone the must understand header check from the
AxisEngine to the MessageReceiver.
Well I am not going to agree on this , since MR is something that people
can write and plug so adding must understand checking into custom code
is not a good idea. Any way must understand checking happen just before
calling the MR ,so to solve the problem you can add a handler just
before the MR and do you logic processing. So I am not going to +1 for
this change.
For example, in case of jaxws handler, an application can choose to
implement getHeaders() and choose to add valid header qnames in that
implementation. A mustUnderstand validation needs to happen for this
scenario as described in section 10.2.1 of jaxws specification, in
this situation if the jaxws handlers are not loaded, the must
understand checks has to be postponed from AxisEngine until the
handler are loaded and available in jaxws implementation.
Currently all the must understand processing happens in AxisEngine's
receive() method, I would like to provide a facility in AxisEngine
code where we can choose to delegate MustUnderstand Check to a Message
Receiver. I would like to propose addition of a new interface called
MessageReceiverExtension in Kernel module which has a method
isMustUnderstandCheckPostponed, this new interface will be implemented
by JAXWSMessageReceiver and will help in making the runtime decision
to postpone must understand check in AxisEngine code.
We can easily fixed this by adding a handler as I mention above , so we
do not need this new Interface.
Thank you,
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
