Ultimately when Java code meets the physical platform, the low-level characteristics (e.g. directory
permissions for the folders that Java code tries to create) are determined by that platform. So, here,
maybe your "umask settings" came into play? e.g. when you deployed an app in the server that
was started as a Java process by some user on that machine, it's that user's umask settings that
determine the permissions on Unix platforms.
Maybe none of this is what's happening on your system. But it has got to be something similar
because I don't think deployment code in GlassFish does "chmod" explicitly on application
folders. There is use of explicit chmod in glassfish source code, but it is at different place (or
so I hope).
-Kedar
[Message sent by forum member 'km' (kedar.mhaswade_at_sun.com)]
http://forums.java.net/jive/thread.jspa?messageID=388060