Mule
  1. Mule
  2. MULE-3003

MuleEvent.getEndpoint() endpoint type is ambiguous

    Details

    • User impact:
      Medium
    • Similar Issues:
      MULE-1486Ambiguous SMTP dispatch with several endpoints
      MULE-2225Ambiguous Schema?
      MULE-2266Remove ENDPOINT_TYPE_SENDER_AND_RECEIVER endpoint type.
      MULE-2300Endpoint types inconsistent
      MULE-5196Ambiguous bean naming causes spurious errors with parent bean context
      MULE-2996Ambiguous Schema
      MULE-2267Endpoint getOrCreate methods that allow type to be specified do not always return endpoints of that type
      MULE-2254Set endpoint type at endpoint creation time rather than in runtime
      MULE-2255Make setting of endpoints on routers, router collections and exception strategies type-safe.
      MULE-5072Rename <simple-service/>'s type from 'default' to 'direct' to better convey its meaning

      Description

      This attribute in some case is used for an inbound endpoint, and in other cases for an outbound endpoint which seems to be a bit ambiguous and therefore not ideal

      • Should MuleEvent has origenEndpoint and destinationEndpoint attributes?
      • Should we have MuleInboundEvent and MuleOutboundEvent?
      • It's OK that this attribute is ambiguous. The type of endpoint changes depending on if it's pre-component or post-component?

        Issue Links

          Activity

          Transition Time In Source Status Execution Times Last Executer Last Execution Date
          To Do To Do Closed Closed
          1205d 15h 8m 1 Daniel Feist 08/Jun/11 09:19 PM

            People

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

              Dates

              • Created:
                Updated:
                Resolved:
                Fix Release Date:
                12/Sep/11

                Development