[ https://jira.jboss.org/jira/browse/JBSEAM-4235?page=com.atlassian.jira.pl... ] Dan Allen commented on JBSEAM-4235: ----------------------------------- I have a prototype available in Seam 2.1 and 2.2 branches (SVN). This is a tough problem because the invocation of an MDB is fundamentally different from a session bean or any other component. Instead of the application getting a reference and invoking the instance, it's the container that does this work. Thus, there is little opportunity for Seam to get its hands in there and enhance it. Simply adding @Asynchronous to the onMessage() method won't do anything at all. I have come up with two approaches that will work. #1. An EJB interceptor - ContextualMessageHandlerRequestInterceptor Apply this interceptor to your MDB as follows: @Interceptor(ContextualMessageHandlerRequestInterceptor.class) public class MyListener implements MessageListener { ... } Now you can use Component.getInstance() from within onMessage() to look up request-scoped, application-scoped, or business-process scoped components. To use a business-scoped component, you must pass either taskId or processId as a Long property in the payload of the message object. #2. A contextual callback Alternatively, you can use the technique that the interceptor uses to execute code within the boundaries of a Seam life cycle. There is some convenience baked in. You can provide as a type parameter the type you want to pass to Component.getInstance() to retrieve your delegate component. try { new ContextualMessageHandlerRequest<MyMessageProcessor>(message) { @Override public void process() throws Exception { getDelegate().process(getTextMessage().getText()); } }.run(); } catch (Exception e) { // log me or something } Internally, this will call: ((MyMessageProcessor) Component.getInstance(MyMessageProcessor.class)).process((TextMessage) message).getText()); Let me know what you think about these solutions. -- 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