Mule
  1. Mule
  2. MULE-4068

Template references methods as optional but they are abstract and required to be implemented

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Tools
    • Labels:
      None
    • User impact:
      Medium
    • Similar Issues:
      MULE-3297AbstractTransactionContext is not abstract
      MULE-4067Improve template for MessageReceiver class doesn't work for Polling Receivers
      MULE-7041EventProcessingThread must manage exceptions thrown by implementation classes
      MULE-7838Remove destroy method from LockProvider insterface
      MULE-5917Component class is not a required attribute in mule schema while it is
      MULE-2843Inconsistent life-cycle method behaviour between component implementations e.g. seda/direct
      MULE-84Enhanced entry point resolution that allows for abstract classes and inherited interfaces as parameter types
      MULE-6991postAuth() method does not catch token expiration exception
      MULE-5670Schema issue - Incorrect Inheritance for Transformer Reference
      MULE-2978Config locations in ConfigurationBuilders needs to be abstracted

      Description

      In the template for creating the XXXConnector class for a custom transport the following methods are commented as optional and should be deleted if not required, but are in fact abstract methods in the base class and thus must be implemented:

      doStart
      doStop
      doInitialize
      doConnect
      doDisconnect
      doDispose

        Activity

        There are no comments yet on this issue.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Yagen
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Development