Long term, isn't this the goal? To have a more modular GlassFish where this stuff can be turned on and off?
Regarding JMS, does Glassfish use JMS internally? Is that why it can not be disabled?
Regarding the __timerPool, I suppose that could be pointed to any database source rather than the internal JavaDB source?
But, finally, is it worthwhile essentially maintaining your own GF deployment rather than using the default? Are the disk space differences that much? Or are you after more a memory impact?
You mentioned you're after a standard environment for internal development. If instead you provided a standard GF Domain config.xml, then that would get your users on track immediately, using the approved URLs and servers.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=204551