Mule
  1. Mule
  2. MULE-3244

Component configuration directly on model is not-ideal, confusing and is not extensible.

    Details

    • User impact:
      Medium
    • Effort points:
      3
    • Similar Issues:
      MULE-8858Rename the metamodel classes adding the Model suffix
      MULE-10368Declare the exception mappings for every component once the extension model is part of core.
      MULE-10274Move extension model to the runtime so it can be used to describe any extension.
      MULE-1995Should be able to lookup a Component directly from the Registry
      MULE-9475Allow config level components in the Extensions API
      MULE-10479Description is not populated in the extension model when the operation is declared at the Configuration instead of the Extension
      MULE-10155Add the concept of keywords to the extension model
      MULE-10456Exported types are not declared in the extension model
      MULE-10622Extension model JSON inside a package is not a valid JSON
      MULE-9246SDK: Extend IllegalModelDefinitionException to be more specific when validating the Extension model

      Issue Links

        Activity

        Hide
        Daniel Feist added a comment -

        This issue needs discussion before we can work on this.

        Show
        Daniel Feist added a comment - This issue needs discussion before we can work on this.
        Hide
        Steven Camina added a comment -

        Closing this issue because it affects a very old version of Mule. Please reopen if this is an issue.

        Show
        Steven Camina added a comment - Closing this issue because it affects a very old version of Mule. Please reopen if this is an issue.

          People

          • Assignee:
            Steven Camina
            Reporter:
            Daniel Feist
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development