-
Notifications
You must be signed in to change notification settings - Fork 21
Design Overall
Francesco Chicchiriccò edited this page May 22, 2013
·
11 revisions
| Prev: Approach |
From a high-level point of view, ODataJClient consists of two distinct layers:
-
Engine
Low-level communication layer taking care of actual REST communication and OData entity (de)serialization, exposing methods to hook into the OData protocol for manipulating entities and invoking actions and functions. -
Proxy
This layer will convert any local change to POJOs and any local invocation of annotated interfaces' methods into actual calls to the Engine layer.
ODataJClient engine is there for Java developers that needs to access underlying details of the OData communication protocol. This allows great customization and the possibility to dig into the actual data exchange.
ODataJClient proxy mode is thought for experienced Java developers which are familiar with widespread Java Enterprise and / or Open Source technologies and prefer to interact with OData services at a very abstract level. This allows easy domain integration with complex architectures.
| Prev: Approach |