> As I understand, virtual domain in GF is served by
> separate process anyway.
No, a GF domain runs as a single monolithic process on the server.
You could run a single instance of GF for several developers. If they're submitting full boat WARs to the server, there's no separation of the users and files at that level -- the server will explode the WAR files in to an internal directory, but they'll be owned by the GF process user.
If the users are simply deploying WARs in a pre-populated directory, then you can maintain your user ownership, assuming the GF server has privileges to read the files.
But, frankly, for development, I wouldn't use a shared server. As robust as it is, there's just too many things that developers can do that might require a server restart, though in theory that restart could be scheduled, but even still there are things that developers can possible do that can affect the server on an unscheduled basis that can impact other developers (PermGen leaks come to mind here).
Really depends on how sophisticated your development is and what the users are doing.
> I could install independent GF for each domain on
> different ports. In this case, each GF instance will
> run under own user credentials. It will take 40 Mb
> and inability to have common admin UI for all.
You can't have a common GUI, but you could easily script the CLI with some common shortcuts to do common tasks, where you can specify the domain name and have the work done, or for some common task you can simply loop through the "known" domains and execute each command on the respective domains.
If you're using root only ports, you can use SMF on Solaris to still let GF use the lower numbered ports, but have the process actually owned by a non-root user.
[Message sent by forum member 'whartung' (whartung)]
http://forums.java.net/jive/thread.jspa?messageID=292653