I have some questions about the new interface WireableBinding that was
checked in as part of revision r557195.
1. Is it intended that all bindings should (eventually) implement this
interface, or only some of them? If only some of them, what's the
guideline for which bindings should implement it and which should not?
2. For bindings that don't (yet) implement it (i.e., all the current
extension bindings), what are the limitations on what can be done
with these bindings?
3. This interface introduces three new getter/setter properties:
TargetComponent
TargetComponentService
TargetBinding
How are these set/used for reference bindings by the core wiring
framework? And how are they set/used for service bindings?
4. The core wiring framework is now calling getURI() as part of its
determination of whether or not a binding has an endpoint. Does
this put new obligations on extension bindings to call their setURI()
method even if no "uri" attribute was specified in the SCDL?
5. Are there any other changes that extension binding writers need
to make (or are recommended to make) to fully support the new
multiple bindings support for references with multiplicity and
promotion?
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
