enumeration constraint
is more appropriate than this interface when there are many values in the enumeration
or when display must be localized.public interface ConstraintNomenclature extends Constraint
The constraint must be declared under the element
xs:annotation/xs:appinfo/osd:otherFacets:
where<osd:constraintNomenclature class="com.foo.MyConstraintNomenclature" />
com.foo.MyConstraintNomenclature is
the fully qualified name of the class implementing this interface.
It is also possible to set additional JavaBean properties:
<osd:constraintNomenclature class="com.foo.MyConstraintNomenclature">
<param1>...</param1>
<param2>...</param2>
</osd:constraintNomenclature>
where param1 and param2 are JavaBean properties of the class specified.
For more information, see the JavaBean specification.
See Constraint life cycle.
ConstraintEnumeration,
ConstraintOnNull| Modifier and Type | Method and Description |
|---|---|
Nomenclature |
getNomenclature(ValueContext aContext)
Deprecated.
Returns a sequence of value-label pairs, where the values correspond to the
underlying enumeration of this constraint.
|
checkOccurrence, setup, toUserDocumentationNomenclature getNomenclature(ValueContext aContext) throws InvalidSchemaException
InvalidSchemaException - if a dynamic condition in the data model prevents the execution of this method.