> > What is exactly the blessed way to implement the
> > initialization (and termination) methods for a new service?
> > Will this change for 3.0?
> >
>
> Already changed in 3.0, there is only init() in 3.0. Services
> in 3.0 are no longer coupled to ServletConfig or RunData. To
> start a service early you do the following:
Ok; so 2.1 keeps working with the same not-so-consistent way,
right? I mean, multiple init() methods, etc., right?
One other question: I was looking for the blessed way to get
properties defined for a service. I noticed TurbineGlobalCacheService
does this:
private long cacheCheckFrequency =
TurbineResources.getLong("cache.check.frequency", 5000);
and the property is defined as
services.GlobalCacheService.cache.check.frequency = 5000
So, I thought this is the correct way to get properties for all
services. However, for one of my own services this doesn't work:
services.STFParserService.database=gandalf
The service does
db_ = TurbineResources.getString("database", "default");
and it is ALWAYS getting "default", no matter what I set in
the properties file. Any ideas?
> Jason van Zyl
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
