Questions for this episode of the live show are here: http://www.adam-bien.com/roller/abien/entry/20_years_of_java_mvc
The messaging subsystem in Wildfly is enabled in the standalone-full.xml config (not standalone.xml).
To add a new queue, search for <subsystem xmlns=”urn:jboss:domain:messaging:2.0″>, and then within the <hornetq-server> section, add a new <jms-destinations> if it doesn’t exist already, and define your queue name and JNDI lookup:
<jms-destinations> <jms-queue name="exampleQueue"> <entry name="jms/queue/example"/> <entry name="java:jboss/exported/jms/queue/example"/> </jms-queue> </jms-destinations>
For my own development I frequently rotate between different app servers and different versions, Tomcat, JBoss AS, Glassfish, trouble is when you work with one for a while and then go back to one of the others, you forget key things, like what your admin password was when you last installed/configured a server.
Whatever the reason, there’s a few different approaches to working around this issue with Glassfish, like creating a new domain and copy files from the old to the new, but this question on superuser.com has the best lifesaver response ever… this file has a backup password that you can use for your admin account, even if you have no idea what your original password was – just copy the value from this file: