Re-consider how cross-parameter constraints are represented in metadata API and XML descriptors

Description

Currently cross-parameter constraints are hosted directly on ExecutableDescriptor in the metadata API and the corresponding types in the XML mapping XSD. Return value and single parameter constraints are accessed by navigating to the return value / parameter types.

Should there be an intermediary type for accessing cross-parameter types as well?

Environment

None

Activity

Show:
Gunnar Morling
February 7, 2013, 8:10 PM

: Did you have anything particular in mind with this?

Emmanuel Bernard
February 11, 2013, 3:00 PM

This also affects the Node API: should we add a cross parameter Node

Fixed

Assignee

Emmanuel Bernard

Reporter

Gunnar Morling

Labels

None

Feedback Requested

None

Feedback Requested By

None

backPortable

None

Suitable for new contributors

None

Pull Request

None

backportDecision

None

backportReEvaluate

None

Components

Fix versions

Affects versions

Priority

Major
Configure