[#LEP-7303] Messaging destination configuration hard coded

PUBLIC - Old Liferay Portal (Use Liferay Portal Standard Edition)

Messaging destination configuration hard coded

Created: 30/Aug/08 09:05 AM Updated: 04/Nov/08 10:09 PM

Return to search

Component/s:

None

Affects Version/s:

5.0.1, 5.1.1

Fix Version/s:

None

Time Tracking:

Not Specified

Environment:

All

Description

« Hide

Messaging destinations are hard coded in classes like GlobalStartupAction and SchedulerEngineImpl.

The destinations types and their listeners should be in a configuration file. They should not be hard coded.

All

Comments

Work Log

Change History

FishEye

Sort Order:

[ Permalink | « Hide ]

Michael Han added a comment - 01/Sep/08 01:08 PM - Visible to

Refactoring the configuration of message bus to remove hard coding of message bus destinations. Destinations are now configured inside of messaging-spring.xml. Listeners to destinations are also configured there.

Refactored Scheduler, Wiki, SearchEngine, and Message Boards to use new configuration process.