Raymond Feng wrote:
Hi,
Here is a list of modules related to databinding:
1) databinding: The SPIs and default implementations, also a list of XML
parsing related databindings/transformers
2) databinding-*: Individual databindings such as SDO and JAXB
3) core-databinding:
org.apache.tuscany.sca.core.databinding.module: The module activator
to hook up the databinding framework with core
org.apache.tuscany.sca.core.databinding.processor: The interface
visitor responsible to detect databindings for java interfaces
org.apache.tuscany.sca.core.databinding.transformers: A set of
special transformers that deals with input/output/exception/array
org.apache.tuscany.sca.core.databinding.wire: Interceptors
I assume that you need 1), some modules from 2) and the java interface
visitor from 3), right?
Hmmm I think I only need the data type representation, introspection,
and enough info about databinding-to-databinding transformation
capabilities to validate wires.
So that gives us:
- a subset of (1) as (1) contains much more than I need, and also
depends on module core <cough/>
- all the extensions from (2) but they also depend on core-spi, not sure
what they need from core-spi?
- the java interface visitor from (3).
Would it be possible to trim down the dependencies a bit and/or move
some of these capabilities up/down the layers to get:
- a databinding layer that doesn't depend on core-spi or core
- databinding extensions that plug into that databinding layer
- a core-databinding layer for the live-runtime data handling
- core-databinding extensions that plug into core-databinding?
Looks like we're almost there though, do you think that can be done with
a few class moves and non-breaking changes? Thoughts?
--
Jean-Sebastien
