This short screencasts demonstrates the new application-scoped resources feature available starting with Milestone 4 of GlassFish 3.1. Such resources are bound to a module (war, ear, ejb) and as such they are created on deploy and destroyed when the module is undeployed. Such resources are defined in a file called glassfish-resources.xml and shipped with the archive. These resources are available only from the application they “belong” to which offers some level of security, more configuration flexibility (no resource name collision and different settings for different applications) as well as some level of performance isolation. Application-scoped resources overall provide a single click/single deploy.
