Over a million developers have joined DZone.

Retroactive Interfaces

· Java Zone

Microservices! They are everywhere, or at least, the term is. When should you use a microservice architecture? What factors should be considered when making that decision? Do the benefits outweigh the costs? Why is everyone so excited about them, anyway?  Brought to you in partnership with IBM.

We wanted to add some AoP HttpClient, and had to use Java Proxy which can only proxy an interface. HttpClient 3.0 doesn't have interfaces. So here's how I got around that problem with a "retroactive interface":

  1. create an interface
    public interface IHttpClient {
      int executeMethod(HttpMethod method)
        throws IOException, HttpException;
  2. extend HttpClient, and implement the interface:
    public class MyHttpClient
      extends HttpClient 
      implements IHttpClient {
  3. Use MyHttpClient as the implementation of the proxy. (I can't show the implementation of the proxy, but you should have an idea about the "retroactive interface" at this point)

Any questions?

From http://www.jroller.com/Solomon/entry/retroactive_interfaces

Discover how the Watson team is further developing SDKs in Java, Node.js, Python, iOS, and Android to access these services and make programming easy. Brought to you in partnership with IBM.


Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}