[snip]
Venkata Krishnan wrote:
Hi Sebastien,
Yes, this was what I intended to do initially. But got a bit
concerned about losing the original state of the model after build
time. I was thinking of a Admin or Mgmt function that might display
the original configurations before thing got built i.e. computed or
aggregated. For this I thought its best to have information that was
originially loaded preserved.
The 'ComputedIntents' and 'ComputedPolicies' will only emerge during
the build time. I could not figure out a better place to hold this
information than the model itself.
Well, that's just for explaining the thoughts behind that
implementation. I am open to cutting this out :).
Independent of this change, could you please help me get some clarity
on how we could retrieve the original configurations. Thanks.
- Venkat
If you want to implement an administration tool that shows the original
composites, components, services, references, implementations,
bindings... and policies then just don't call CompositeBuilder.build() :)
Administration tools, wizards, and editors should use the original
models loaded from the development artifacts. CompositeBuilder.build()
refactors and transforms the original assembly model so much (to make it
easier to process at runtime) than preserving only the original policies
wouldn't help anyway.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
