Controller implementation for REST-ws

[Koziolek]

When you will implement this feature take a look at very strong separation between data storage layer and bussiness logic layer. It should be look like

Controller --> EntityGateway --> DataStore (JPA, raw HashMap, file based etc.)

[MirekSz]

Current Operator Controller example is not so bad...ofcourse is connected with Operator Repository which don't have any specific JPA attributes....from the other side it's extends JPARepository, but in very clean way. Spring Data also has base CRUDRepository which can be ported to another datastores like MongoDB.

In my opinion best solution will be
Controller ---------Service ---- ---Repostorory-------- DataStore (JPA, raw HashMap, file based etc.)

The "Core" works on BusinessModel and send to repo(interface) BM objects.
Then RepositoryImpl (JPA, file etc.) thinks how to persists these objects in DS