Sahoo wrote:
> Kedar Mhaswade wrote:
>
>> Huh? Launcher logic is already well defined. (There is a case where
>> an admin might want a domain to start with a specific JDK
>> (java-config_at_java-home) in domain.xml).
>
> I don't understand why an admin would not like to configure that
> information in asenv.conf. If you know why, please share it with us.
I know why. The user can setup a default JDK in asenv.bat -- and then
override the JDK for a particular server instance in domain.xml
Thank you,
Byron
> Any way, if we allowed the admin to configure java-home in domain.xml
> in v2, then I certainly won't advocate for a change. I just hope that
> we keep things simple; the more ways something can be configured, the
> more confusing it becomes.
>
> Thanks,
> Sahoo
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>
--
Byron Nevins Work 408-276-4089, Home 650-359-1290, Cell 650-784-4123 - Sun Microsystems, Inc.