With current jms implementation, if mappedName or <message-destination> in DD is not specified, whether or not destinationLookup/destination is specified in activationSpec is specified, the MDB deployment will fail by error message "missing destination JNDI name". This is incorrect.
It is expected that any single property of destinationLookup, mappedName and destination specified can take effect for sucessful MDB deployment. If all of them are provided, the desired overriding order should be "destinationLookup over destination, and destination over mappedName".
One more thing that can be enhanced is about the error message, which could be misleading: "missing destination JNDI name". It is proposed being changed to "MDB destination not specified".