I've supplied the -ds.xml file, and that works fine. It's the other file that's causing my hernia. I can only assume that I will need the JBoss-5-equivalent of this file in order to use JMS against my MySql db. Thanks for the tip on jboss messaging. It's not too clear, from what docs I've seen, which parts and versions of what components are bundled with JBossAS. For your resources Peter: not-free as in speech, or as in beer? I'll consider either one so long as the cost either way is not too high. I'd love to see what's behind the url you're offering. To add some more thoughts to the original thread: What really impressed me in the past about JBoss was that you could just turn it on, and with a minimum amount of configuration it would just *work*. This was never true for other app servers I've been forced to work with, like Weblogic, Sun JES, or (*shudder*) Websphere. It may not be production battle-ready, but it will at least work. I'm now coming back to JBoss to see what's all involved in a major production outlay, and I'm struggling with *dev* issues. This scares me a bit. Most of this involves the lack of documentation, but it seems subjectively that it's a little bit more complex for the administrator now than it used to be. Maybe it's my imagination. (I seem to remember that documentation was well-available in the days of the JBoss 3 beta.) I was always a bit leery of the JBoss buyout, in terms of the quality of product that would be delivered ever after. Does anyone know what's going on in JBoss's collective consciousness? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4138219#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...