Re: client/server properties split

probably a bit OT, but i'd like to have the opportunity to store such 
stuff in a db. one scenario would be an i18n website, where editors 
could translate huge blocks of text incl. html formatting; here, 
textfiles would not be an option.

but maybe there is already something out there that slipped through my 
fingers?

best,
nils

Raoul Pierre wrote:

> Hello,
>
> I'm working on the i18n of  keel-client/clnt-struts. I need to put 
> somewhere the locale messages and tell keel where to find them.
>
> I'm considering three ways:
> 1/ create a conf/server/system.xconf in keel-client, and in 
> "system-properties"  define the path and name to the messages file. 
> With this elements, create custom system properties in Java.
>
> And same thing in clnt-struts.
>
> Is there any objection to use such a file in keel-client and/or 
> clnt-struts?
>
> 2/ define path and name as "context-param" in web.xml. With this 
> elements, create custom system properties in Java.
>
> 3/ KeelClientUser tries to get properties from a "client.properties" 
> file. Two points here :
> - By decreasing priority order, Keel searches client.properties in:
>     * directory specified by CONFIG_OVERRIDE property, no default value
>     * directory specified by working.dir system property, by default 
> "WEB-INF"
>     * parent directory of the directory specified by working.dir 
> property, i.e. by webapp root directory
>     * directory specified by user.dir property
> For the first place, Keel try to find CONFIG_OVERRIDE property among 
> the system properties, i.e. keel properties defined in system.xconf...
> - plugin.jelly does'nt copy any properties files from such 
> directories, but [keel/logkit/roles/instrument].properties rom 
> {keel_project}
>
> The proposition here is: plugin.jelly copies "client.properties" from 
> {keel_project} directory to the webapp root directory. And then Keel 
> reads in it the path and name to the messages file.
>
> I prefer the first option, then the second one.
>
> Any other idea?
>
> Pierre
>
>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com