Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [corona-dev] Is CORONA_CONFIG_HOME still needed?

Since CORONA_CONFIG_HOME can be defined as a system property (in
config.ini), should it following the naming convention used by
config.ini?

Example: corona.config.home

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Kaczmarek, Pawel
Sent: Monday, April 16, 2007 5:03 AM
To: Corona development
Subject: RE: [corona-dev] Is CORONA_CONFIG_HOME still needed?

  It is not necessary to set CORONA_CONFIG_HOME, but it will be used if
set.
If CORONA_CONFIG_HOME is not set, the default location will be used.
  If set, CORONA_CONFIG_HOME points to the location of system container
and newly added containers.
  Pawel

-----Original Message-----
From: corona-dev-bounces@xxxxxxxxxxx
[mailto:corona-dev-bounces@xxxxxxxxxxx] On Behalf Of Marcin Okraszewski
Sent: Friday, April 13, 2007 2:13 PM
To: Corona development
Subject: Re: [corona-dev] Is CORONA_CONFIG_HOME still needed?

I think it is also used as a place, where new containers are stored.

Marcin


O'Flynn, Dennis wrote:
>
> I believe CORONA_CONFIG_HOME is a server side property that defines 
> where to find the SystemContainer.
>
>
------------------------------------------------------------------------
>
> *From:* corona-dev-bounces@xxxxxxxxxxx 
> [mailto:corona-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Jaworowski,
Piotr
> *Sent:* Friday, April 13, 2007 4:38 AM
> *To:* Corona development
> *Subject:* 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 *Everitt, Glenn
> *Sent:* Friday, April 13, 2007 12:20 AM
> *To:* Corona development
> *Subject:* [corona-dev] Is CORONA_CONFIG_HOME still needed?
>
> 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.
>
>
> 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.
>
>
> 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.
>
------------------------------------------------------------------------
>
> _______________________________________________
> corona-dev mailing list
> corona-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/corona-dev
>   
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. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

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. 
_______________________________________________
corona-dev mailing list
corona-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/corona-dev

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. 


Back to the top