Message bus interface too complicated with send(Object), send(String)

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.1.1
• Fix Version/s: 5.1.2
• Component/s: None
• Labels: None
• Environment: All
• Similar Issues: Show 5 results ; ;

  LEP-7614	Sending DLFileEntries to the Message Bus
  LEP-7304	Implementation of scheduling service too tightly coupled
  LEP-5851	SecureFilter BASIC authorization is too complicated and should try logging in with screenname, uid, and email
  LEP-6006	Message bus should support unique message id
  LEP-6065	Sending synchronous messages through the message bus

The current message bus implementation is too complicated with the ability to send either String or Objects. It also does not contain all the necessary facilities to deal with synchronous message sending, reply to destinations, etc.

[Michael Han]

Modified MessageBus interface to remove send(String, String) and send(String, Object). Simplified to send(String, Message) where Message has the necessary envelope information and payload details.
Modified MessageListener interface to remove receive(String, String) and receive(String, Object). Simplified to receive(Message).
Refactored all implementations of MessageListener and all users of MessageBus to accomodate for new interface changes.
This change lays the groundwork for simplifying the synchronous messaging implementation to be done in later.

WARNING - This involves interface changes and will impact both users of MessageBusUtil and the listeners that implement MessageListener

[Michael Han]

already done in 5.1.2