Version 1 by Thor Henning Hetland
on Jul 06, 2009 17:13.

compared with
Current by Bård Lind
on Apr 04, 2011 15:52.

This line was removed.
This word was removed. This word was added.
This line was added.

Changes (2)

View Page History
h3. Motivation

We want our H2A services to be easy to use and to give great service/value.

h3. Argumentation

Too generic webparts or portlets just moves the complexity to the configuration and shall be avoided. Usually these services are just a very thin presentation layer, which is more easily duplicated than generalized. Too general H2A services actually cost more to configure than it cost to duplicate.

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:P7. Too generic webparts or portlets shall be avoided]