With major credits to: http://jira.codehaus.org/browse/XFIRE-490, have
managed to get the SOAP action set in a workaround way.
First created the handler class, which accepts the action I want then, once
I've created my service, I add the following line to get the SOAPAction in
the HTTP header:
Client.getInstance(service).addOutHandler(new
SOAPActionHandler("http://mynamespace.com/Login";));
/**
* HandlerClass to add the SOAPAction HTTP header
*/
public class SOAPActionHandler extends AbstractHandler {
private String SOAPAction;
public SOAPActionHandler(String SOAPAction) {
setPhase(Phase.TRANSPORT);
after(SoapActionInHandler.class.getName());
this.SOAPAction = SOAPAction;
}
public void invoke(MessageContext context) throws Exception {
context.getExchange().getOutMessage().setProperty(SoapConstants.SOAP_ACTION,
SOAPAction);
}
}
This works and is good enough. It's not very clean though. I could
probably inspect the MessageContext to determine the operation, and combine
that with the namespace to get my SOAPAction. Maybe later...
--
View this message in context:
http://www.nabble.com/SoapAction-tf3703322.html#a11065570
Sent from the XFire - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
