Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Fix For: 1.1 (Proposed) In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment.

Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Assignee: Pete Muir Fix For: 1.1 (Proposed) In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment.

Thanks. On 24 Aug 2012, at 18:27, Nigel Deakin wrote: > Pete, > > On 24/08/2012 15:12, Pete Muir wrote: >> Nigel, >> >> Could you cast your eye over https://issues.jboss.org/browse/CDI-151 and check that it does make sense? >> >> Related spec section is at http://docs.jboss.org/cdi/spec/1.0/html/contexts.html#d0e5377 > > I spotted this the other day and wondered about it. The references to a javax.jms.MessageListener are a little > ambiguous. > > There are two ways in which messages can be delivered to a MessageListener in Java EE: > > 1. In the Java EE EJB container, applications can define a message-driven bean which implements > javax.jms.MessageListener. > > 2. In the Java EE application client container (or Java SE), applications can define any class they like which > implements javax.jms.MessageListener, create an instance, and register it using the JMS API. However applications > running in the Java EE web or EJB containers are forbidden from doing this (this prohibition is in the platform > spec). > > When the CDI spec 6.7.3 refers to "message delivery to a MessageListener", which of the above is it referring to? > > If it is referring to (1) then this is already covered in the preceding bullet point which mentions "message > delivery to any EJB message-driven bean". > > If it is referring to (2) then this really only makes sense if the application context is active in other places in > the application client as well. Since there is no other mention of the application client I suspect this was not > intended. CDI doesn't require support for application clients, so I guess it must be referring to (1). Are you ok with me pasting this conversation into the issue?

I'll resolve it by just deleting that text :-)

Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Assignee: Pete Muir Fix For: 1.1 (Proposed) In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment.

Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Assignee: Pete Muir Fix For: 1.1.PRD In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment.

Remove from section 6.7 JMS notes --------------------------------- Key: CDI-151 URL: https://issues.jboss.org/browse/CDI-151 Project: CDI Specification Issues Issue Type: Clarification Reporter: John Ament Assignee: Pete Muir Fix For: 1.1.PRD In section 6.7, a reference is made to JMS Message Listeners. MessageListeners (as bound to the consumers) are not available in JMS in an EE environment.