Mule
  1. Mule
  2. MULE-2821

Inconsistent component type name

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Trivial Trivial
    • Resolution: Fixed
    • Affects Version/s: 2.0.0-RC1
    • Fix Version/s: 2.0.0-RC2
    • Component/s: Core: Configuration
    • Labels:
      None
    • User impact:
      Low
    • Similar Issues:
      MULE-2787inconsistent class name attribute type
      MULE-2948inconsistencies with entrypoint resolver schema names
      MULE-2843Inconsistent life-cycle method behaviour between component implementations e.g. seda/direct
      MULE-1983Component names not checked for uniqueness / no namespacing
      MULE-2300Endpoint types inconsistent
      MULE-5851Inconsistent MBean naming of Mule statistics creates usability issues
      MULE-7455Inconsistent payload type when calling http endpoint from a flow with http inbound endpoint
      MULE-2902transformerRefType name is inconsistent
      MULE-748Axis WSDL generation uses inconsistent namespaces
      MULE-8390Obtain component name in ComponentMessageNotificationListener

      Description

      The component types in mule.xsd have a name ending in "ComponentType" – "pojoComponentType", "defaultComponentType" The one exception is "NoArgsCallWrapperType"

        Activity

        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open In Progress In Progress
        3h 32m 1 Travis Carlson 19/Dec/07 02:01 PM
        In Progress In Progress To Be Merged To Be Merged
        28s 1 Travis Carlson 19/Dec/07 02:02 PM
        To Be Merged To Be Merged Closed Closed
        48s 1 Travis Carlson 19/Dec/07 02:02 PM

          People

          • Assignee:
            Travis Carlson
            Reporter:
            Ted Bashor
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development