[ https://jira.jboss.org/jira/browse/JBSEAM-4237?page=com.atlassian.jira.pl... ] Nikolay Elenkov updated JBSEAM-4237: ------------------------------------ Attachment: async-container.patch MDP container patch -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4237?page=com.atlassian.jira.pl... ] Nikolay Elenkov commented on JBSEAM-4237: ----------------------------------------- I have attached a patch that allows you to create MDP containers in your WAR project. This allows you to have any Seam component that implements javax.jms.MessageListener receive JMS messages asynchronously. How to use it: 1. Create an application scoped Seam component that implements javax.jms.MessageListener: @Name("myListener") @Scope(ScopeType.APPLICATION) public class MyListener implements MessageListener { public void onMessage(Message message) { log.info("got message: " + message); } } 2. Add the following to components.xml <jms:async-message-listener-container auto-create="true" startup="true" name="jmsContainer" destination-jndi-name="queue/A" listener="#{myListener}" exception-listener="#{myListener}" outjected-session-name="myListenerSession" /> * destination-jndi-name: JNDI name of your queue/topic * listener: your POJO implementing MessageListener * exception-listener: an optional javax.jms.ExceptionListener, it gets called on connection errors * outjected-session-name: if defined the underlying session is outjected to application scope. You can use it to commit JMS transactions and reply to messages in your listeners. The patch has only been (minimally) tested on JBoss 4.2.2, but should work on any AS, as long as you can lookup the ConnectionFactory and destinations via JNDI. More details in the JavaDoc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4237?page=com.atlassian.jira.pl... ] Jason Porter commented on JBSEAM-4237: -------------------------------------- I like what you've done Nikolay. I created something very similar a while ago to listen to Queues just to see if it would work, proof of concept work really. Looks like we have a use for it after all though, so I think I'll take the work you've done and add listening to Queues to it. I'll attach patches (full) as I get to them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-4237?page=com.atlassian.jira.pl... ] Jason Porter commented on JBSEAM-4237: -------------------------------------- Sorry Nikolay, I didn't read through the code with a fine enough comb :) I'll give it a shot in a proof of concept project and see how it goes. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira