[
https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin....
]
Brett Meyer commented on ARTIF-645:
-----------------------------------
In a demo with Teiid/JDV, they had a great thought about why this would be important. It
would allow extensions to provide their own JCR CNDs and configurations for existing,
external data sources. The custom contract implementations would know what to do with the
data, providing integration with Artificer without having to port all artifacts into
Artificer-specific models.
Allow users to supply extensions through a new plugin architecture
------------------------------------------------------------------
Key: ARTIF-645
URL:
https://issues.jboss.org/browse/ARTIF-645
Project: Artificer
Issue Type: Feature Request
Reporter: Brett Meyer
Assignee: Brett Meyer
The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which
allows users to contribute, among other things, UI components (!!!). A similar structure
could be extremely valuable for Artificer. Things a plugin could contribute:
- extension contract impls (ArtifactBuilder, TypeDetector, etc.)
- JCR node types (assuming we're able to change the spec to allow /s-ramp/[custom
model]/[custom type]
- UI elements (custom metadata displays, custom actions, etc.)
- endpoint bindings (again, /s-ramp/model/type)
Eric's demo:
https://bluejeans.com/s/82tW/
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)