Jon,
A possibility to customize the TurbineServices instance would be useful in
integration to different environments than a typical servlet engine.
Instead of (01/30/2001):
public class TurbineServices extends BaseServiceBroker
{
private static ServiceBroker instance = new TurbineServices();
public static ServiceBroker getInstance()
{
return instance;
}
protected TurbineServices()
{
}
}
Something like this:
public class TurbineServices extends BaseServiceBroker
{
protected static ServiceBroker instance;
public static ServiceBroker getInstance()
{
if (instance == null)
{
synchronized(TurbineServices.class)
{
if (instance == null)
instance = new TurbineServices();
}
}
return instance;
}
protected TurbineServices()
{
}
}
Would allow subclasses to assign their own service broker implementation to
the static instance member before getInstance() is called.
-- Ilkka
--
Nokia Networks
http://www.nokia.com/networks
mail: [EMAIL PROTECTED]
> -----Original Message-----
> From: ext Jon Stevens [mailto:[EMAIL PROTECTED]]
> Sent: 28. January 2001 21:34
> To: Turbine
> Subject: Services
>
>
> Please,
>
> Don't touch the services classes. I'm working on them and
> touching them will
> cause conflicts. I'm re-working the whole initialization
> scheme because it
> is just blatantly wrong right now.
>
> :-)
>
> -jon
>
>
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
> Problems?: [EMAIL PROTECTED]
>
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]