arch@glassfish.java.net

Re: V3 Installer one pager is ready for review

From: Bill Shannon <bill.shannon_at_sun.com>
Date: Mon, 12 Jan 2009 13:39:44 -0800

http://wiki.glassfish.java.net/attach/V3FunctionalSpecs/V3FinalInstallerOnePager.txt


For the desktop and browser integration features that are missing on Mac OS,
how much of those features are implemented by OpenInstaller, and how much
of those features are implemented by the JDK? I thought the JDK handled
browser integration and runtime desktop integration. Is it only install
time desktop integration that's the problem - adding things to the "start
menu" and such?

Ludo also asked on the forum about Mac OS dmg installer support, does
OpenInstall have any such support?

Does IzPack do a better job of supporting Mac OS?

For the silent install file, the names of the properties are, how shall I
say, bizarre! Are these names completely arbitrary, or are they derived
from something else, say from Java class names?

I don't understand why there is both glassfish.Administration and
glassfish.AdministrationExtended.

Why do a bunch of the new properties start with "A_"?

Why "RegistrationOptions.regopts", isn't that redundant?

I think we'll want the "Dist Types" to be more human-friendly, marketing-chosen
names like "Java EE" and "Web Profile", but I don't think we've chosen the
final names for those yet.

Does the GlassFish installer depend directly on zlib? Isn't all the zlib
functionality available through the JDK in java.util.zip? Or shouldn't zlib
be used by OpenInstaller instead of the GlassFish installer?

In asadmin create-service and delete-service, what are the required args
that you're depending on these commands supporting?

I don't understand 4.11, bullet 4. If the silent file has encrypted passwords,
how do I encrypt a password to store in that file? Won't it need to be both
encrypted and base64 encoded? How is the decryption password supplied during
the silent install? I didn't see a command line argument to supply it. Does
that mean that silent installs always have to be interactive so you can read
the password from the terminal after prompting?