Hi,
so far we've been merging the former 'engine' module from ODataJClient
into odata4-client-api and odata4-client-core (there is still a lot to
do, of course).
There are, however, more modules we need to merge from ODataJClient:
1. test-service - a simple CXF-based application which acts as V3 and
V4 service (with static back-end) for integration tests of the 'engine'
and 'proxy' modules (Fabio is working to complete this as per OLINGO-175)
2. maven-plugin - the Maven plugin for generating POJOs to be used
with the 'proxy' module
3. proxy - Inspired by JPA, this layer will convert any local change
to POJOs and any local invocation of annotated interfaces' methods into
actual calls to the Engine layer.
While (2) and (3) will be merged later, we need to find the right place
for (1) ASAP in order to start merging all remaining components and
integrations tests from the 'engine' module.
I'd propose for (1) a new top-level module (at the same level of
odata4-lib) named odata4-test-service.
WDYT?
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Involved at The Apache Software Foundation:
member, Syncope PMC chair, Cocoon PMC, Olingo PPMC
http://people.apache.org/~ilgrosso/
