For pluggable eoperations implementations

For graph elements implementing property source.
Use processor property - fully qualified name of a class to instantiate.
If contains :: then a static method.

Shall take no arguments or two arguments - requirement and progress monitor.
If both flavors are available then the second one takes precedence as more specific.

The result is reflectively wired.

I want do use the cli command for generating an ecore doc using cli. But i cant find a release of the cli tool or an doc hot to build this.

E.g. subnet in azure-networking would also be available as azure-subnet.

Pkg. Exports annotation? String list or map

From the registry and configs. To delegate.
Processors is another option.

Or loaders, to customize loading.
Exec call yaml

Load keys ? Aliases

Contributor extends.
Can modify, replace, and discard object - return null. Use for enrichment - load from yaml and enrich with info pulled from systems or vice versa.

For ecore pkgs and classifiers and features

Derived - same identifier and transitive. Cache.

For graph elements which implement property source use properties to create a processor which executes a script:

• script
• script-language
• script-ref

For script-ref use extension if script-language is not provided.

Wire the resulting processor using annotations - test with Groovy.

Add a section to the documentation page.

In the future add support for namespaces, custom script creation using the requirement object.

Currently SpEL is the hardcoded expression language for reflective wiring annotations (https://docs.nasdanika.org/core/graph/index.html#wiring).

With the introduction of the capability framework it makes sense to add support of multiple expression languages:

• Add expressionLanguage attribute to annotations which evaluate expressions. Set default to spel
• Create ExpressionLanguageRequirement record taking language name
• Add SpEL capability factory in the capability module
• Add Groovy capability factory in the groovy module (create)
• For annotations in common (Reflector) - create a subclass in Capability (CapabilityReflector) overriding methods which evaluate expressions, keep SpEL as default in common, throw UnsupportedOperationException for languages other than SpEL
• Update Javadoc in annotations which use SpEL
• Also update AbstractDrawioFactory and documentation