On Thu, Jan 21, 2010 at 2:46 PM, Raymond Feng <[email protected]> wrote: > We have two options here: > > 1) Call all types of PolicyBuilder to populate the default values into the > model > 2) Call all types of PolicyProviderFactory to give them the opportunity to > enforce the default behavior (The current code supports this flavor). > > Option 1 is interesting to explore. If it happens, the builders will add the > default values to the in-memory assembly model when the intents/policySets > are absent in the SCDL. PolicyProviderFactory can then be registered by the > policy types. Tuscany runtime will look them up from the > ProviderFactoryExtensionPoint by the type and call them to configure the > invocation chain. >
What are the side effects of using option1 and then using the in memory model to write the composite, will we start to get very different composites being produced ? Would this have effects on tooling runtimes that have this as a common pattern for reading/writting composites to files ? -- Luciano Resende http://people.apache.org/~lresende http://lresende.blogspot.com/
