Hi,
It's a challenge but it also opens a good opportunity for us the figure out
how to align the SCA composition hierarchy with the databinding model
scopes.
I think there will be two perspectives on both the Tuscany and the
databinding sides.
1) How does the databinding framework support the pluggable scoping for its
typing system (if it can)?
2) What're the isolation/sharing/visibility rules for the databinding types
in the context of the composite hierarchy?
BTW, we already started a thread on scoping for SDO types.
Thanks,
Raymond
----- Original Message -----
From: "Jeremy Boynes" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, June 08, 2006 7:07 AM
Subject: Type definitions in composites, was: [PATCH] Porting SDO
DataBinding to the new SPI in Jeremy's sandbox
Thanks Raymond - I'll work on applying this.
I think you've identified a key issue here - how does a databinding's
type system mapping work in the new recursive model?
In the 0.9 view, modules were flat so it was easy to make the
association between a module and a TypeHelper. Recursion opens up new
questions such as:
* should there be a heirarchy of types to match the hierarchy
of composites?
* what are the sharing rules for types? Are all types shared between
a parent composite and its children? Are none?
* if a type is defined in multiple places in a hierarchy,
which one is used?
Any thoughts on how we would like this to work?
--
Jeremy
Raymond Feng wrote:
Hi, Jeremy.
Attached is a patch for the SDO DataBinding code in your sandbox. It
ports the code to the new SPIs in the sandbox. Please review and
apply.
There're several TODOs in the code. We need to understand how to get
the corresponding SDO TypeHelper for a given DeploymentContext.
Thanks, Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
