Mule
  1. Mule
  2. MULE-5751

Allow to programmatically distinguish internal MessageProcessor

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Critical Critical
    • Resolution: Fixed
    • Affects Version/s: 3.3.0
    • Fix Version/s: 3.4.0
    • Component/s: Core: Event/Message
    • Labels:
      None
    • User impact:
      Low
    • Similar Issues:
      MULE-3357Update Configuring Mule Programmatically page on 2.0 wiki
      MULE-7665Allow size of internal buffer to be defined via MuleConfiguration and <configuration> config element
      MULE-7092DevkitBasedMessageProcessor does not implement MessageProcessor
      MULE-3216Internal mechanism to allow customization of inbound/outbound message processing pipelines using MP API (was: Implement endpoint features/extensions)
      MULE-25Make programmatic event dispatching a bit more intuitive
      MULE-7664Allow size of internal buffer used for copy streams to be customized via system property
      MULE-8287Allows cipher suite configuration per connector
      MULE-6672pattern:http-proxy not allowing []
      MULE-6883pattern:http-proxy not allowing []
      MULE-5948enricher element causing error trying to set property messageProcessors

      Description

      It would be nice to have some programmatic way to distinguish internal MP from MP matching application configuration.
      At list a full list of those is required.

        Activity

        Hide
        Ray Sayre added a comment -

        Made this a blocker for 3.2.0 but it could be deferred to 3.2.1

        Show
        Ray Sayre added a comment - Made this a blocker for 3.2.0 but it could be deferred to 3.2.1
        Hide
        Ray Sayre added a comment -

        Changed priority to Unassigned because the use-case is not clear. The problem originated from using the now defunct tracking:listener feature that allowed programmatic access to mule notifications

        Show
        Ray Sayre added a comment - Changed priority to Unassigned because the use-case is not clear. The problem originated from using the now defunct tracking:listener feature that allowed programmatic access to mule notifications
        Hide
        Ray Sayre added a comment -

        Changed back to blocker, my comment about this being just for tracking:listener was incorrect.

        Show
        Ray Sayre added a comment - Changed back to blocker, my comment about this being just for tracking:listener was incorrect.
        Hide
        Ray Sayre added a comment -

        Conclusion from meeting btw Dan, Julien, Ray on 9/14/2011: use a marker interface to distinguish the MP class types

        Show
        Ray Sayre added a comment - Conclusion from meeting btw Dan, Julien, Ray on 9/14/2011: use a marker interface to distinguish the MP class types
        Show
        Santiago Vacas added a comment - 3.x: http://fisheye.codehaus.org/changelog/mule/?cs=24884 http://fisheye.codehaus.org/changelog/mule/?cs=24885 http://fisheye.codehaus.org/changelog/mule/?cs=24886 http://fisheye.codehaus.org/changelog/mule/?cs=24895 http://fisheye.codehaus.org/changelog/mule/?cs=24905 http://fisheye.codehaus.org/changelog/mule/?cs=24919 http://fisheye.codehaus.org/changelog/mule/?cs=24925 http://fisheye.codehaus.org/changelog/mule/?cs=25035

          People

          • Assignee:
            Santiago Vacas
            Reporter:
            Julien Eluard
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development