WSDL2Java should generate some kind of infrastructure on the server side for
soap:headers defined in WSDL
---------------------------------------------------------------------------------------------------------
Key: AXIS2-2793
URL: https://issues.apache.org/jira/browse/AXIS2-2793
Project: Axis 2.0 (Axis2)
Issue Type: Bug
Reporter: Glen Daniels
Right now we generate extra parameters on Stubs for <soap:header>s on the
client side. We do not do any equivalent for the server side skeletons. This
is potentially a problem in that if one of the headers is sent at runtime with
MustUnderstand="true", we'll get a fault even though we should understand the
header.
Proposal is to define an "ApplicationHeaderHandler" which reads metadata from
AxisService describing which headers the service understands. It a) checks to
see that those headers are present in the message (faults if not), b) marks
them as processed so MU test works, and c) supplies the OMElements in
convenient properties of the MessageContext.
--
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]
