OK. So what you were exploiting previously is that GlassFish MQ allows you to
call MessageConsumer.setMessageListener in a Java EE application, even though
the Java EE spec states that applications must not do this. This has not
changed in GlassFish 4 because (even though it was forbidden in the spec) we
didn't want to disrupt existing GlassFish applications. However
JMSConsumer.setMessageListener, which is a new method in in GlassFish 4, does
enforce this restriction. From a spec perspective, there isn't a "legal" way
to create an async consumer on a temporary destination (and there has never
been). I'll log this as a possible issue for the next version of the JMS
spec.
--
[Message sent by forum member 'nigeldeakin']
View Post: http://forums.java.net/node/900071