If someone takes this one, let me know.
Related to this job, I'm working on the user/password set when the JMS manager is deployed. The mechanism that works for the XML state manager is not ported yet.
Additionally, Since 2.3.4 will ship with the Hibernate SAR I am considering using that as the persistence abstraction for the JMS persistence manager, so that there is no need to maintain a JMS-DS SAR for each database.
I created a separate topic for the hibernate persistence manager and state manager.
Part (2) of this requirement has been implemented.
It is possible to run sql statements when creating queues to populate the database.
This is really intended for the testsuite and configuring the default guest.
In practice you would not want to store passwords in plain text.