I notice that we now have a: | public static synchronized void deliverToDeadLetterChannel(Message message) throws RegistryException, MessageDeliverException { | if (dlQueueInvoker == null) { | dlQueueInvoker = new ServiceInvoker(INTERNAL_SERVICE_CATEGORY, DEAD_LETTER_SERVICE_NAME); | } | dlQueueInvoker.deliverAsync(message); | } | operation in ServiceInvoker. Although I can understand the necessity for this (make it easier to send specifically to the DLQ), I disagree with the approach. Why not subtype ServiceInvoker and have a specific DLQServiceInvoker? That way we also encourage others to use the SI approach in an extensible and manageable way. Plus, if someone wants to deliver something synchronously to the DLQ we don't have to go back and change the SI interface again. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4070842#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...