On Aug 15, 2006, at 9:58 AM, Raymond Feng wrote:
As defined by the SCA spec, we are allowed to add extensions to the
SCDL model, for example, we can add "myExtension" to a "composite"
as illustrated below.
<composite ...>
<ns1:myExtension xmlns:ns1="http://my.extension/";>
...
</ns1:myExtension>
</composite>
With the current extensibility story, I can register a loader to
load the "myExtension" XML stanza to creat "MyExtensionDefinition"
model object. Is the CompositeLoader supposed to add the
"MyExtensionDefinition" instance returned from my loader to its
extension map using ModelObject.getExtensions().put(...,
myExtensionDefinition) if it doesn't belong to the base SCDL model?
Assuming the answer is yes, then I would like to register a builder
to create the runtime metadata out of the MyExtensionDefinition
(AFAIK, this extensibility doesn't exist today) and attach it to
the owning SCAObject (unfortunately, SCAObject interface doesn't
have the extensions).
Why would this go on the runtime artifact as it sounds like we are
mixing runtime with model? Wouldn't it be better to handle this in
the model loading?
Does this requirement make sense? It comes out as I investigate the
"import.sdo" story.
Thanks,
Raymond
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
