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?
Thanks,
Raymond
--------------------------------------------------
From: "Jean-Sebastien Delfino" <[EMAIL PROTECTED]>
Sent: Wednesday, April 23, 2008 1:28 AM
To: "tuscany-dev" <[email protected]>
Subject: Using a subset of the databinding framework
I'm writing sample admin tasks that need to work with our models
(implementations, interfaces, policies) to inspect SCA artifacts, build
them, wire them, package them etc.
I don't want to have to drag the whole Tuscany runtime in these tasks or
have to bootstrap the runtime layer (activator, runtime contexts,
service/reference providers, invokers, wireprocessors etc).
How can I get the proper subset of the databinding framework suitable for
use in that non-runtime environment?
Can I just use a subset of the databinding-* modules? or do I need to
split some of these modules to avoid runtime dependencies?
Thanks
--
Jean-Sebastien