Uploaded image for project: 'Artificer'
  1. Artificer
  2. ARTIF-645

Allow users to supply extensions through a new plugin architecture

    Details

    • Type: Feature Request
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      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.)
      • JPA entities
      • UI elements (custom metadata displays, custom actions, etc.)
      • endpoint bindings (again, /s-ramp/model/type)

      Eric's demo: https://bluejeans.com/s/82tW/

      The architecture should allow plugins to be deployed as JARs within Wildfly. In addition, our built-in plugins should also be delivered that way, allowing users to opt-in (rather than always take the performance hit of needlessly using the Switchyard/Teiid/RTGov plugins).

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                brmeyer Brett Meyer
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated: