So far the discussions seam to mostly relate to a single application, our need is a little more advanced
We deploy many different self contained versions or our application to the same application server. This is required as it would be a waste of resources to use a single instance of jboss for each appication.
We have both production systems, QA systems and of course dev systems.
Our application's EAR contains the configuration for the JMS resources needed for each app (multiple topics and queues per instance of the app)
We also have a standalone -ds.xml file for each ear so our systems administrators can point these apps to the right databases
The "global" configuration introduced in AS7 works fine in the case where you only have a single application in any given jboss instance as it can be pre-configured by the system admins and then the app deployed. It does not work so well when you wish to hot-deploy a new application to the server and wish to migrate apps between application servers.
It also currently requires that system admins know more about the "internals" of the application as they now need to build the JMS resources, rather than let the developers deal with these. So this now requires that system administrators need to re-config the application server for a specific version of our app for example if the latest version adds a new JMS queue
It would be possible for system admins to login to the web and configure the database connections prior to deploying an app, but that feels like going backwards in term of flexibility and currently there is no similar method to define JMS resources, so it's impossible to hot deploy new apps in AS7 that require JMS due to the lack of web admin for this aspect