AbstractOptionalV1_Get the list of builders for class instance value.
OptionalV1_Get the list of serializers for class instance value.
OptionalV1_Get the list of deserializers for class instance value.
OptionalV1_Get the list of transformers for class instance value.
OptionalV1_Get the list of builders for dataset entitlement report.
OptionalV1_OptionalV1_Get the list of builders for dataset specification.
OptionalV1_Get the list of serializers for dataset specification.
OptionalV1_Get the list of serializers for dataset specification.
OptionalV1_Get the list of transformers for dataset specification.
OptionalV1_Get the list of builders for packageable element: i.e. protocol model -> metamodel.
OptionalV1_Get the list of methods to derive the classifier path of a packageable element.
OptionalV1_Get list of element pointer type
OptionalV1_Get the list of de-serializers for packageable element: i.e. JSON -> protocol model.
OptionalV1_Get the list of serializers for packageable element: i.e. protocol model -> JSON.
OptionalV1_Get the list of transformers for packageable element: i.e. metamodel -> protocol model.
OptionalV1_Get the list of builders for function expression.
NOTE: this process is complicated, as it involes advanced procedures like type inferencing, function matching, handling generics, etc. so our graph manager never intends to even try to do this. However, occassionally, when there is needs to understand some particular lambda (such as while building a query), we would need this method.
OptionalV1_Get the list of serializers for Graph Fetch.
OptionalV1_Get the list of serializers for Graph Fetch.
OptionalV1_Get the list of type inferrers for property expression.
OptionalV1_Get the list of builders for query execution (mapping, runtime).
OptionalV1_Get the list of supported system element models.
NOTE: since this set of element is meant to be kept small at the moment, we can store them as part of the codebase; however, when this set grows, we should consider having a backend exposed an end point to collect these models.
Plugins for protocol processors. Technically, this is a sub-part of
PureGraphManagerPluginbut due to the way we encapsulate the protocol code and the way we organize graph managers, we want to keepPureGraphManagerPluginto operate at metamodel level where as this allows extension mechanism on the protocol models.When we introduce another version of protocol models, e.g. v2_0_0, we would just add another set of plugin methods here without having to modify the abstract layer of graph manager.