Allow to programmatically distinguish internal MessageProcessor

Details

  • Type: Improvement Improvement
  • Status: Closed 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:
    None

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

Ascending order - Click to sort in descending order
Hide
Permalink
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
Permalink
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
Permalink
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
Permalink
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

People

  • Assignee:
    Santiago Vacas
    Reporter:
    Julien Eluard
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: