So why does this deploy and run without errors on some other Java EE Servers, but glassfish complains? Answer: Glassfish is much more security conscious.
Ken Paulsen has a really good blog about his experience getting jive to run on GlassFish. Right away he gets an exception because the security manager is restricting permissions on the application. Above is a quote from his blog where he details how to configure the GlassFish security manager to relax permissions or simply turn it off. Turns out this isn't the first time users have seen this issue. Vince ran into the same thing when he tried to get Equinox running on GlassFish.
Last month we featured a blog by Felipe titled "Do you want security in your App Server?" as he found most servers run with the security manager disabled by default. I have to wonder if application writers really prefer security managers disabled or if they simply don't realize that they are developing to that environment.