If CLASSPATH is not set, it is defaulted to the current directory. If you set the CLASSPATH, it is important to include the current working directory (.). Otherwise, the current directory will not be searched. A common problem in running hello-world program is: CLASSPATH is set but does not include the current working directory. Petr Jiricka 2010-07-23 11:55:56 UTC Mac OS X 10.5.8 1. How to format usb thumb drive for windows and mac. Register WebLogic under the services node 2. Go to the server properties, Platform tab The value of Java Home is set to ', and as a result WebLogic does not start. Furthermore, the value is not editable, so I can not corrected manually. The correct Java Home on my machine is: /System/Library/Frameworks/JavaVM.framework/Versions/1.6/Home Here is the error in the output tab after starting the server: The JRE was not found in directory. (JAVA_HOME) Please edit your environment and set the JAVA_HOME variable to point to the root directory of your Java installation. ![]() Denis Anisimov 2010-07-23 12:12:14 UTC Please provide details: - is it consequence of changed customizer? The customizer doesn't allow to change JDK home. AFAIK ( this is true for Win at least ) there is no possibility to set JAVA_HOME for WL start script ( see details on the issue about WL Customizer ). This variable is 'hardcoded' in the start script file ( at WL installation process ). So this issue is not customizer issue but installer. For checking this could you please attach two files: - setDomainEnv.sh - startWebLogic.sh in 'bin' directory of your weblogic domain ( you can find its path in Customizer ). Denis Anisimov 2010-07-23 12:53:04 UTC JAVA_HOME is set by 'setDomainEnv.sh' script. There is no sense to set JAVA_HOME variable manually because it will be overridden by this script. And I don't see any code in WL plugin which set up this variable. Thanks for the script files. I've got the problem: this is specific Mac OS issue. As result I will need to change UI for Customizer. I was thinking that there could be only two Java vendors: Oracle and Sun. But this is not true. There can be a number of different vendors. For Mac case this is Apple vendor with its own JDK path. This case requires Customizer UI change. Petr Hejl 2010-07-23 13:08:56 UTC Allowing the JDK change seems to be bit ambitious at this phase. I think parsing the startup script which can change with every minor release and can contain high number of different java vendors. I would suggest to have just not editable text field displaying the used JDK. In such case you have a fallback of displaying 'Unable to detect'. In future when you get pretty sure about settings you can change such textfield to combobox. I even think the non editable field should be enough as change of JDK for server is pretty rare imo and you just configure it on installation. Petr Hejl 2010-07-23 13:29:31 UTC (In reply to ) > I agree that JDK textfield should be non-editable. > This is exactly how it is done now. I'm sorry I was inaccurate. What I meant was to remove the Java vendor configuration and to keep just JDK text field. If it would be manageable *and* useful we can change the text field to combo later (that would change vendor in background not java_home). I would not allow to change vendor and/or java_home now.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. АрхивыКатегории |