{"id":137,"date":"2019-08-02T10:58:05","date_gmt":"2019-08-02T10:58:05","guid":{"rendered":"http:\/\/www.matez.de\/?p=137"},"modified":"2019-08-02T10:58:06","modified_gmt":"2019-08-02T10:58:06","slug":"fault-tolerance-for-jax-ws-with-resilience4j","status":"publish","type":"post","link":"https:\/\/www.matez.de\/index.php\/2019\/08\/02\/fault-tolerance-for-jax-ws-with-resilience4j\/","title":{"rendered":"fault tolerance for jax-ws with resilience4j"},"content":{"rendered":"\n

In a recent project, we still have to use SOAP webservices and I wanted to apply some resilience pattern such as retry <\/a>to my project.
Also a collegue just presented a java library called resilience4j<\/a> so I wanted to use that one.<\/p>\n\n\n\n

Of course, there are a lot of other possibilites like using other libraries (like Hystrix) or applying the sidecar pattern<\/a> outside of my application in a cluster. <\/p>\n\n\n\n

As you can see in the documentation<\/a>, resilience4j is build for functional programming style and it supports some functional interfaces
which can be decorated to apply the retry mechanism to the function invocation. In the examples, you can always find a simple setup to pass the supplier and decorate it only for the particular method.<\/p>\n\n\n\n

In my use case, I do not want to write the decoration code for each and every method (or function). I have a third party WSDL, generated the webservice interface and port via wsimport <\/a>and now I want to generically apply the retry mechanism to the webservice client. But my solution is not very complicated, it is using a reflection proxy and invocation handler to direcly decorate and execute the method via the Retry classes.<\/p>\n\n\n

\n
\n
\n \n
\n
\n \n
\n\n \n
\n\n