|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (2)
View Page Historyh3. Motivation
h3. Argumentation
It is the responsibility of the portlet framework/application to be the coordinating framework. If the H2A services start stepping on the toes of its surroundings, we end up with chaos.
h3. Exceptions/special cases
h3. Definitions
h3. Status
|| Doc status || [H2A] || [A2A] || [ACS] || [CS] || Last [PAB] discussion ||
| (/) | (+) | (-) | (-) | (-) | 2007.06.08 |
----
h3. PAB discussions
-----
h3. [Design-Time Governance - SOA Design Rules FAQ]
{include:Design-Time Governance - SOA Design Rules FAQ}
h3. Argumentation
It is the responsibility of the portlet framework/application to be the coordinating framework. If the H2A services start stepping on the toes of its surroundings, we end up with chaos.
h3. Exceptions/special cases
h3. Definitions
h3. Status
|| Doc status || [H2A] || [A2A] || [ACS] || [CS] || Last [PAB] discussion ||
| (/) | (+) | (-) | (-) | (-) | 2007.06.08 |
----
h3. PAB discussions
-----
h3. [Design-Time Governance - SOA Design Rules FAQ]
{include:Design-Time Governance - SOA Design Rules FAQ}
Content moved to [OWSOA:P5. A H2A Service (webpart or portlet) shall be a part of a bigger whole, not trying to dictate other H2A services]