Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call a new method of ClientInterceptor when sending the message failed [SWS-778] #862

Closed
gregturn opened this issue Jun 5, 2012 · 1 comment

Comments

@gregturn
Copy link
Member

@gregturn gregturn commented Jun 5, 2012

Pierre Le Roux opened SWS-778 and commented

Hello,

ClientInterceptor handleResponse or handleFault aren't called when the process send a message to a remote server and this server doesn't answer (404...).
It's normal because no soap response message has been sent.
It could be interesting to have another function, for example : handleException or handleError in order to get the deal the request status when server doesn't answer a compliant message.

I know there are ExceptionResolver and I'm already using it but i need such a method for doing the process below :

  • In my ClientInterceptor, I track sent message and current time in handleRequest
  • I'm already tracking soap response and current time at response
  • I can't track response time and http status (or JMS...) when connexion fails...

If needed, I can add my class which is in an opensource project.


Referenced from: commits ac030c2

@gregturn
Copy link
Member Author

@gregturn gregturn commented Mar 18, 2014

Arjen Poutsma commented

Fixed by adding an afterComplete callback to ClientInterceptor, similar to the existing one in EndpointInterceptor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants