| Use the config.ini for parameterized delivery [message #541661] |
Tue, 22 June 2010 01:53  |
Eclipse User |
|
|
|
Inside of the config.ini in the server it is possible to override the member variables of services.
For example:
com.bsiag.mnet.server.services.common.sql.SqlService#directJ dbcConnection=true
If the service SqlService has a setter method for the member directJdbcConnection then the member has at runtime the value true.
With Scout Eclipse this works for all classes which extends AbstractService
For other classes it must be done by yourself for example with the class FilterConfigInjection at startup.
|
|
|
|
|
|
|
| Re: Use the config.ini for parameterized delivery [message #545118 is a reply to message #545112] |
Tue, 06 July 2010 12:58  |
| Eclipse User |
|
|
|
Interesting, thanks for the update.
I'm sure this should work well for server-side Eclipse applications, but I
can't imagine client applications making regular use of it.
Most apps store their properties elsewhere, e.g. in .meta-inf, even if
they're not primarily IDE style.
STEM does, and that way projects are more easily to use across teams. You
wouldn't want to copy the config.ini from one system to another.
|
|
|
| Re: Use the config.ini for parameterized delivery [message #581381 is a reply to message #544504] |
Tue, 06 July 2010 10:36 |
| Eclipse User |
|
|
|
every Eclipse installation contains a file
[yourEclipseDir/configuration/config.ini] where bundle properties can be
defined. This file has nothing to do with any underlying OS.
No, Scout applications are not operating system deptendent. At
EclipseCon 2010 we did a tutorial covering mac, linux and windows os.
Cheers Andreas
Werner Keil wrote:
> ..ini, does that mean, the server or Scout as a whole is limited to
> Windows?!
|
|
|
|
| Re: Use the config.ini for parameterized delivery [message #581419 is a reply to message #545111] |
Tue, 06 July 2010 12:29 |
| Eclipse User |
|
|
|
Basically every service member having a setter method can be initialized
with a config.ini property.
e.g.
package com.bsiag.services;
public class MyService extends AbstractService{
private boolean m_foo;
private String m_bar;
public void setFoo(boolean foo){
m_foo = foo;
}
public void setBar(String bar){
m_bar = bar;
}
}
config.ini:
com.bsiag.services.MyService#foo = true
com.bsiag.services.MyService#bar = aValue
Werner Keil wrote:
> Well most applications use the standard properties like OSGi, etc.
> Is there a complete list of those Scout extends, at least on the server?
>
> Thanks,
> Werner
|
|
|
| Re: Use the config.ini for parameterized delivery [message #581433 is a reply to message #545112] |
Tue, 06 July 2010 12:58 |
| Eclipse User |
|
|
|
Interesting, thanks for the update.
I'm sure this should work well for server-side Eclipse applications, but I
can't imagine client applications making regular use of it.
Most apps store their properties elsewhere, e.g. in .meta-inf, even if
they're not primarily IDE style.
STEM does, and that way projects are more easily to use across teams. You
wouldn't want to copy the config.ini from one system to another.
|
|
|
Powered by
FUDForum. Page generated in 0.05075 seconds
Home