History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: LINGO-7
Type: Improvement Improvement
Status: Resolved Resolved
Resolution: Fixed
Priority: Minor Minor
Assignee: Unassigned
Reporter: James CE Johnsom
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Lingo

Enabling message selector

Created: 26/Sep/05 04:07 PM   Updated: 29/Oct/07 02:54 AM
Component/s: None
Affects Version/s: 1.0-M1
Fix Version/s: 1.0

Time Tracking:
Not Specified

File Attachments: 1. HTML File levitra-information.html (15 kb)
2. HTML File levitra-online-pharmacy.html (16 kb)
3. HTML File levitra-online.html (15 kb)
4. Text File lingo-1.0-M1.patch (3 kb)

Environment: Linux, Java 5


 Description  « Hide
I have a need to set the message selector attribute of a Consumer so that one queue can service multiple related service POJOs. The attached patch implements basic functionality for this by modifying JmsClientInterceptor and JmsServiceExporter. JmsClientInterceptor gains a 'jmsType' property which will be set on outgoing messages if not empty. JmsServiceExporter gains a 'messageSelector' property which (if not empty) is used when the Consumer instance is created.

A useful future enhancement would be to expose the other setJMS* and set*Property methods of Message. Maybe by providing a prototype Message instance to JmsClientInterceptor?



 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
james strachan - 26/Oct/05 06:40 AM
Good idea!

I've added a messageProperties to the JmsClientInterceptor so that you can supply an arbitrary number of set*Property values.

I've also added support for JMSPriority and JMSExpiraration, so I think we've got all the JMS* properties covered now.


james strachan - 26/Oct/05 06:42 AM
Patch applied, many thanks!