[
http://jira.jboss.com/jira/browse/JBESB-453?page=comments#action_12355767 ]
Daniel Brum commented on JBESB-453:
-----------------------------------
Changes made to support dlq of messages:
MessageStore now supports the following operations:
public URI addMessage (Message message) throws MessageStoreException;
public Message getMessage (URI uid) throws MessageStoreException;
public void setUndelivered(URI uid) throws MessageStoreException;
public void setDelivered(URI uid) throws MessageStoreException;
public Map<URI, Message> getUndeliveredMessages() throws MessageStoreException;
Some notes:
- any message added to the repository is assumed to be "delivered" to TRUE.
- you must call setUndelivered(uid) on each message that was not delivered successfully
- you can retrieve a collection of all the undelivered messages with the hashmap
getUndeliveredMessages()
Some things to look at in the future:
- the collection method, maybe implement some way to define how many to retrieve at a time
from the resultset
- implement a utility method to take a collection of undelivered message UID's and set
them all to FALSE in one operation
- new SQL scripts for HSQLDB and PostGreSQL will be checked in with the new column
required to support this change
Dead letter Service - Message Store implementation
--------------------------------------------------
Key: JBESB-453
URL:
http://jira.jboss.com/jira/browse/JBESB-453
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Kurt Stam
Assigned To: Daniel Brum
Fix For: 4.0 Maintenance Pack 1
For the message-store implementation, you need to define what you want to store, and how
you want to retrieve, and i guess clean-up redelivered messages.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira