One of the backends is exposing its API as RESTFUL services. These services are needed by several portlets. So we thought to consume them from a service builder module and use the module from the portlets (like we do in database access).
The problem is that, we see many recommendation to use spring RESTTemplate to consume the rest services, but we can't use them in our service builder, are we missing something?
We thought of using spring portlets directly, but I want the REST client to be exposed to any current of future portlet without repeating the code in each portlet.
The problem is that, we see many recommendation to use spring RESTTemplate to consume the rest services, but we can't use them in our service builder, are we missing something?
Why not?
The biggest issue you face will be the use of "fake entities", a thing that I've blogged about and have championed in the past because it allows you to build out a "service layer" that is based on a general data sink instead of a specific database table.
That still applies in LR7/DXP, but you might also be able to leverage simple OSGi DS service implementations as well.
