Jean-Sebastien Delfino wrote:
Mike Edwards wrote:
Folks,
A thought here is whether we should be keeping around all of the
original SCDL at all times.
I can regard the Domain as consisting of the SCDL made up from all the
contributions made into it. I have the view that the Domain is a kind
of distributed database of configuration information. I think this is
separate from the runtime information within Tuscany which is an
implementation of the "design" laid down in the Domain configuration.
So perhaps the idea should be to always keep the Domain information
(XML form if desired) and to reference it from the runtime entities.
That way, it will be always possible to go back and retrieve the
original Domain configuration information.
Thoughts?
Yours, Mike.
+1 to all that
The runtime uses a "compiled" optimized model different from how the
model was expressed in the original XML.
I think we need to keep the original form (as you said XML if desired)
in the domain, when new XML is added go back to the XML and re-"compile"
it, then hand the new "compiled" form to the runtime.
Twisting the "compiled" model to keep some of the original XML and patch
it when new XML is added will be too complicated and won't work.
>
I don't think it's twisting the compiled model to retain the original
information, especially when it's not possible to recover this from the
compiled model. For debugging and error reporting, it's useful for the
runtime to know about the original SCDL so that error reporting can be
done in terms of what the user sees and not (for example) by exposing
runtime-generated binding names that aren't the ones the user provided,
and in the worst case might even collide with user-specified names.
The overhead of retaining this information (at least in the case being
discussed) is small.
Patching the runtime model to update it with new XML is a different
discussion that introduces more complex issues than simply retaining
the user's view of the configuration for diagnostic purposes.
Simon
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
