Class XQueryFunctionAnnotationHandler

  • All Implemented Interfaces:

    public class XQueryFunctionAnnotationHandler
    extends java.lang.Object
    implements FunctionAnnotationHandler
    Function annotation handler for annotations in the built-in namespace This defines the annotations %public and %private, and the (XQuery Update 3.0) annotations %updating and %simple
    • Constructor Detail

      • XQueryFunctionAnnotationHandler

        public XQueryFunctionAnnotationHandler()
    • Method Detail

      • check

        public void check​(AnnotationList annotations,
                          java.lang.String construct)
                   throws XPathException
        Description copied from interface: FunctionAnnotationHandler
        Test whether a given set of annotations in this namespace is valid.
        Specified by:
        check in interface FunctionAnnotationHandler
        annotations - the annotation list (filtered by namespace: all the annotations will have names in the namespace for this annotation handler)
        construct - the construct on which this list of annotations appears. One of "DF" (declare function), "DV" (declare variable), "IF" (inline function), "FT" (function test)
        XPathException - if the annotation is invalid, or if it is inconsistent with the annotations in the existing list.
      • getAssertionNamespace

        public NamespaceUri getAssertionNamespace()
        Get the namespace handled by this function annotation handler. This handler will only be called in respect of annotation assertions that are in this namespace. Use the empty string to refer to the null namespace
        Specified by:
        getAssertionNamespace in interface FunctionAnnotationHandler
        the namespace handled by this function annotation handler, namely ""
      • satisfiesAssertion

        public boolean satisfiesAssertion​(Annotation assertion,
                                          AnnotationList annotationList)
        Test whether a function with a given list of annotations satisfies an annotation assertion present on a function item test.
        Specified by:
        satisfiesAssertion in interface FunctionAnnotationHandler
        assertion - the annotation assertion present in the function item test
        annotationList - the annotations present on the function being tested
        true if the assertion is satisfied, false if not
      • relationship

        public Affinity relationship​(AnnotationList firstList,
                                     AnnotationList secondList)
        Test the relationship of one list of annotation assertions to another list of annotation assertions, all from this namespace

        The lists will always be non-empty, because it is assumed that a test with an empty list of assertions always subsumes a test with a non-empty list.

        Specified by:
        relationship in interface FunctionAnnotationHandler
        firstList - the first list of annotation assertions
        secondList - the second list of annotation assertions
        the relationship between the two lists, as one of the values Affinity.SAME_TYPE, Affinity.DISJOINT, Affinity.OVERLAPS, Affinity.SUBSUMES, Affinity.SUBSUMED_BY. For example, if the first list is %colour("blue") and the second list is %colour("green"), and no function can be both blue and green, then return DISJOINT. But if a function can have more than one colour, return OVERLAPS because the set of functions conforming to the two assertions has a non-empty intersection. If the first list is %colour("any") and the second list is %colour("blue"), then return SUBSUMES, because the set of functions satisfying the first assertion is a superset of those satisfying the second assertion.

        The result of this method must be consistent with the satisfiesAssertion(Annotation, AnnotationList) method. For example, if this method indicates that %big subsumes %huge, then it must indeed be the case that the set of functions that satisfy the assertion %big is a superset of those that satisfy the assertion %huge.

        If in doubt, it is always safe to return OVERLAPS: the worst that can happen is that type-checking is deferred until run-time.