Re: Relying on Http error codes with AXIS
Hi, As a follow-up I use this code in the client OperationContext oct = stub._getServiceClient().getLastOperationContext(); MessageContext mct = oct.getMessageContext(WSDLConstants.HTTP_HEADER ); It doesn't print the http headers. Thanks, Mohan -- View this message in context: http://www.nabble.com/Relying-on-Http-error-codes-with-AXIS-tp18150103p18191532.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Relying on Http error codes with AXIS
Hi, REST-based styles and the SOAP web service differ. Our client relies on the Http transport error codes to find out if the SOAP/Http request has reached or not. There are two styles being mixed here. Does anyone have an opinion about this ? Can the Http 200 come to the client even if the SOAP/Http request has not been processed by the Axis engine but the http layer has processed it successfully. The protocols are different here ? Thanks, Mohan -- View this message in context: http://www.nabble.com/Relying-on-Http-error-codes-with-AXIS-tp18150103p18150103.html Sent from the Axis - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
