It has nothing to do with scheduling as far as I know. If you want to remove a message just consume it (But you need to identify the message in some way)

See http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=

This is not what I suggested. To remove the message you have to identify, right? Otherwise how can you say 'I want to remove that message because the client wants to cancel something''.

I wasn"t saying 'check the ID and say do not activate. I was saying "please JMS give the message ID blablabla' and instead of doing something with it, just forget about it and close the session (that will have as effect that the message will be removed from the queue).

I don't understand why this concept is so difficult to understand. If you want to remove A message, you need a way to identify it, right? So you need, either the JMSMessageID, either your own ID mechanism, put as a JMS header (see my previous link for full details).

Is it clear?

Regards,

Stephane

>But I cannot agree with this for Scheduled Delivery.
>Since there may be a possibility of deleting >messages before it got received?.

Schedule delivery is just a message sitting in the queue and waiting for the delivery time. If you want to cancel this message, just 'receive' it manually. That is create a receiver to receive only that message (using a selector) and that 's it.

Something like:

if (action.getAction().getType().equals(Action.Type.CANCEL)) {
logger.info("Cancelling notification with ID [" + action.getNotificationID() + "]");

String selector = Constants.NOTIFICATION_ID_PROPERTY + " = '" + action.getNotificationID() + "'";
JmsReceiverLocal jmsReceiver = JmsReceiverUtil.getLocalHome().create();
Message m = jmsReceiver.receive(notificationQueue, selector);

if (m == null) {
logger.warn("no notification with ID [" + action.getNotificationID() + "] was found");
} else {
logger.info("Notification with ID [" + action.getNotificationID() + "] canceled successfully");
}

// send response
} else {
logger.error("Action [" + action.getAction() + "] not yet supported");
}

Where notificationID is a ID I set on the message (it could be JMSMessageID, in that case you don't have to set anything, just to keep a reference of the message somewhere)

Regards,

Stephane

> Can you please post an example that you have already worked out with MDB.

Mmmm I start understanding why you do not understand ... Your MDB is there to get fired with a message (let's say in 7 days). If some component before that period consume the message, your mdb will not be fired (so your component cancel the message, right?)

What you need is a Session Bean that creates a receiver and the receive and consume that message. (see code snipper above - JmsReceiverSessionBean is a bean that can fetch data in a queue using a selector).

Regards,

Stephane