| RE: [corona-dev] Is CORONA_CONFIG_HOME still needed? |
|
I’ve searched the code for
CORONA_CONFIG_HOME, this system variable is used in SystemContainerAdministrator class. I guess we should wait for Pawel to tell
us if those are still valid warning messages. Cheers, Piotr From:
corona-dev-bounces@xxxxxxxxxxx [mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of I am getting these warning when I start the Corona Server –
are these valid warnings or should they be removed? [WARN] [2007.04.12 04:42:26 EDT]
[org.eclipse.corona.container.services]: CoronaLogManager is not available; log
level settings won't work. [INFO] [2007.04.12 04:42:26 EDT]
[org.eclipse.corona.container.services]:
[{org.osgi.service.event.EventHandler}={event.topics=[org/eclipse/corona/log/NEW_LOGLEVEL],
service.id=50}]: ServiceEvent REGISTERED [ERROR] [2007.04.12 04:42:26 EDT] [org.eclipse.corona.container.services]:
Specified system environment variable CORONA_CONFIG_HOME is not a directory. [ERROR] [2007.04.12 04:42:45 EDT]
[org.eclipse.corona.container.services]: Plugin preferences CORONA_CONFIG_HOME
value is not a directory. Possible bug! [WARN] [2007.04.12 04:42:45 EDT]
[org.eclipse.corona.container.services]: CORONA_CONFIG_HOME value was not
specified. Setting default directory as corona configuration. [INFO] [2007.04.12 04:42:52 EDT] [org.eclipse.emf.commonj.sdo]:
BundleEvent STARTED
The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. |