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

Key
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 the H2A services to be reusable building blocks.

h3. Argumentation

WebParts and portlets shall be self-contained components to be conform to the specification and to be reusable in different scenarios and contexts. It is also very important to be able to automatically test the service in isolation, which is almost impossible if you break this rule.



h3. Exceptions/special cases


----
h3. Definitions


h3. Status

|| Doc status || [H2A] || [A2A] || [ACS] || [CS] || Last [PAB] Discussion ||
| (/) | (+) | (-) | (-) | (-) | 2007.06.08 |


----
h3. PAB discussions

It is OK to create (Web) Applications on top of a SOA, these applications may choose to use H2A services ot to call directly services in other categories. It is important to separate applications and H2A services.
-----

h3. [Design-Time Governance - SOA Design Rules FAQ]

{include:Design-Time Governance - SOA Design Rules FAQ}
Content moved to [OWSOA:P4. A H2A service (webpart or portlet) shall be an independent component]