All I am saying is java for a domain *can be* configured in domain.xml
for a server and launcher has to take care of that. Asadmin, on the other
hand, till V2, was using JDK configured *only* in asenv. If we now have
to support the java in the path of asadmin shell, we should change
asadmin script like:
if (javaFromAsenv points to wrong JDK)
then
JAVA=java from path
fi
JAVA ...CLIMain.
That should take care of all the cases.
-Kedar
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. 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
>