Geek asks and answers

Spring Roo + GWT: Does RequestFactory still work if double control is required for every data operation?

One of the requirements of our application is the implementation of "double control" for everything, including CRUD operations. To be clear, “double control” is a function that requires a change in the data that must be approved by someone other than a change request. Therefore, when the user makes changes to the data, he is not directly tied to production tables. I am aware of several ways to implement this (e.g. staging tables), but this at a different time.

The question is, with such a requirement, do you think we should follow the standard "data-oriented" way generated by Roo + GWT (which uses RequestFactory)?

Or is it better for us to implement our own "command template" structure to support dual control?

I am inclined to the latter. My intuition (based on a 3-day game with Roo + GWT) says that RequestFactory is not designed for double control, and we will hit the wall if we try to get inside. It would be more than happy to be mistaken here.

+3
source share
2 answers

Have you looked at RequestFactory ServiceLayerDecorator? It mediates all interactions between payload processing and objects and domain code. As an example, you can override methods getProperty, and setPropertyto read and write to some shady magazine containing deferred mutations.

ACL , , loadDomainObject resolveX , .

, RequestFactoryServlet two-arg. , SimpleRequestProcessor, , ServiceLayer.create().

: RequestFactory ServiceLayerDecorators; GWT, ServiceLayerDecorator. , , API ServiceLayer, , getTop(). , ServiceLayerDecorator , , , ThreadLocal, RequestFactoryServlet.getThreadLocalX().

+4

, " " , , , "" , , " " ( ).

diffs, RequestFactory ( , ) , setProperty, , , ( : "" diff ThreadLocal, ). "" , diff ; diff .

, " " , " "; "" " ", "".

, ( ), , / " " " CRUD" (.. "" "", " ", "" ).

+3

More articles:


All Articles