[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [camp] Groups - camp-spec-v1.1-wd08-issue-4-v2-gp.doc uploaded
Suppose there was a PDP that contained to Components, A and B.
Suppose A had a requirement X and B had a requirement Y. We register this PDP on platform "Foo". For whatever reason, the implementation of Foo represents A and B as separate Application Component Templates. After completing the registration operation, Foo contains a ACT-A (corresponding to Component A) and a ACT-B (corresponding to Component B). It turns out that Foo had PCTs that were good matches for X and Y, PCT-X and PCT-Y respectively. Either by auto-wiring or my direct manipulation by the Application Admin, ACT-A gets linked to PCT-X and ACT-B gets linked to PCT-Y. Now suppose we register our PDP on platform "Baz". For whatever reason, the implementation of Baz rolls A and B up into a single ACT. Although Baz has combined A and B into a single ACT, it must preserve the requirements of each component - so ACT-AB would have two requirements, X and Y. If you resolved these requirements against PCTs (assuming Baz has the appropriate PCTs), you would see ACT-AB linked to both PCT-X and PCT-Y. None of this addresses how the code and configuration in A and B actually go about connecting to or using the service represented by the PC that the PCT is a template of - but that's a separate issue. ~ gp On 4/13/2013 9:17 AM, Alex Heneveld
wrote:
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]