Currently using RC1 for client invocations
Has anyone have any ideas why the org.apache.axis.client.Call resets the
message context on invoke().
public void invoke() throws AxisFault {
if (log.isDebugEnabled()) {
log.debug("Enter: Call::invoke()");
}
Message reqMsg = null ;
SOAPEnvelope reqEnv = null ;
msgContext.reset(); <-- Offending code call.
This effectively clears the context of anything set via a client call like
...
Hashtable moreHeaders = new Hashtable();
moreHeaders.put("ABC", "123");
call.getMessageContext().setProperty(HTTPConstants.REQUEST_HEADERS,
moreHeaders);
env = call.invoke(env);
By the time the context is used by the transport component
(org.apache.axis.transport.http.HTTPSender), there are no longer any custom
header entries.
Bug or not ?
Is there any other way to effect a custom http header entry?
