Eclipse Community Forums: Eclipse Scout » How to access settings from config.ini

Help

Home

Home » Eclipse Projects » Eclipse Scout » How to access settings from config.ini

Show: Today's Messages :: Show Polls :: Message Navigator

How to access settings from config.ini [message #1053719]

Tue, 07 May 2013 11:36

Urs Beeli

Messages: 573
Registered: October 2012
Location: Bern, Switzerland

Senior Member

I've tried to access some of the settings defined in the config.ini file of the server product (say org.eclipse.scout.rt.server.services.common.file.RemoteFileService#rootPath) but not found out how to do that.

How would I go about accessing those settings?

Report message to a moderator

Re: How to access settings from config.ini [message #1053728 is a reply to message #1053719]

Tue, 07 May 2013 12:04

Jeremie Bresson

Messages: 1252
Registered: October 2011

Senior Member

I am not sure what you mean.

This line in config ini:

org.eclipse.scout.rt.server.services.common.file.RemoteFileService#rootPath=SomeValue

Correspond to:

service.setRootPath("SomeValue");
//where service is the instance of org.eclipse.scout.rt.server.services.common.file.RemoteFileService

(of course it is dynamic, but I think you get the idea)

I am not sure when the properties are set:
* 1. during scout server start.
* 2. during Service initialization.
(I think it is the second solution, but I didn't check).

You can access the value with:

SERVICES.getService(RemoteFileService.class).getRootPath();

I hope it helps.

Report message to a moderator

Re: How to access settings from config.ini [message #1053882 is a reply to message #1053728]

Wed, 08 May 2013 06:16

Urs Beeli

Messages: 573
Registered: October 2012
Location: Bern, Switzerland

Senior Member

Thanks, this works perfectly for rootPath.

What if I wanted to add arbitrary application specific configuration settings to the config.ini file that I would want to access?

Report message to a moderator

Re: How to access settings from config.ini [message #1056875 is a reply to message #1053728]

Wed, 08 May 2013 12:03

Urs Beeli

Messages: 573
Registered: October 2012
Location: Bern, Switzerland

Senior Member

Quote:

I am not sure what you mean.

SERVICES.getService(RemoteFileService.class).getRootPath();

Thanks, this was part of what I wanted and it works perfectly for rootPath.

What if I wanted to add arbitrary application specific configuration settings to the config.ini file that I would want to access?

Report message to a moderator

Re: How to access settings from config.ini [message #1057723 is a reply to message #1053728]

Wed, 08 May 2013 13:09

Jeremie Bresson

Messages: 1252
Registered: October 2011

Senior Member

Urs Beeli wrote on Wed, 08 May 2013 14:04

What if I wanted to add arbitrary application specific configuration settings to the config.ini file that I would want to access?

In this case, you do not need the special pattern:

<Class>#<property>=<value>

I think that this pattern is specific to Eclipse Scout. It is a good practice when you want to configure some parameter on a generic service (RemoteFileSerivce, SQL Service...). The advantage of having a such configuration in a config.ini file is that you can modify it during your deployment process (if you need to deploy for test and for production)

If you want a normal property: just use the pattern (like in any *.properties file)

<property>=<value>

For example:

my.property=lorem

You can access the value with:

Activator.getDefault().getBundle().getBundleContext().getProperty("my.property");

Report message to a moderator

Re: How to access settings from config.ini [message #1057737 is a reply to message #1057723]

Wed, 08 May 2013 13:57

Arthur vD

Messages: 52
Registered: March 2010

Member

Hi

If you extend an org.eclipse.scout.service.AbstractService and add a field with a setter and a getter you can use the myPackage.MyService#myFieldName=myValue style lines in the config.ini. For your own classes not extending AbstractService you can use ServiceUtility.injectConfigProperties(this) to inject the properties. You'd still have to have a field following the bean conventions.

Have fun.

EDIT: Or use the free style properties as Jeremie has explained.

[Updated on: Wed, 08 May 2013 13:59]

Report message to a moderator