Skip to end of metadata
Go to start of metadata

Motivation

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

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.

Exceptions/special cases

Definitions

Status

Doc status H2A A2A ACS CS Last PAB discussion
2007.06.08

PAB discussions


Design-Time Governance - SOA Design Rules FAQ

  • [Question still to be asked..]
Labels:
policy_h2a policy_h2a Delete
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.