From: Clebert Suconic <clebert.suconic_at_gmail.com>
Date: Fri, 22 Jul 2011 12:11:38 -0500

shouldn't we make a change here. It's a common question in our forums
about why Message.setPriority is ineffective?


e.g.:

http://community.jboss.org/message/616993?tstart=0#616993
http://stackoverflow.com/questions/6788240/jms-message-priority-not-working-on-message


I confess that this confused even me at some point.


IMO, someone should be able to change the priority at the message
level also. I.e. if Message.setPriority was called, the provider would
be able to use that priority instead.

I don't want to open a JIRA without discussing this first.

My suggestion is we either allow Message.setPriority to change the
priority individually or we deprecate Message.setPriority.