>
> Currently:
>
> Turbine.init() calls
> TurbineResources.setPropertiesFileName() calls
> TurbineResources.init() calls
> TurbineServices.getInstance().getService(RESOURCES) calls
> TurbineResourceService.init() calls
> new TurbineResources() which calls
> TurbineResources.init()
>
> infinite loop
>
> So I commented out the call to init() in the TurbineResources constructors
> as a quick fix but...
>
> IMO TurbineResources should have been left a straight singleton until the
> services.resources stuff was firmed up. Currently, there is nothing in
> services.resources that manages multiple resources from files. If we want a
> "resource service" then having a TurbineResourceService associated with a
> single props file doesn't get us very far.
>
> Also, making the methods in TurbineResources static is convenient but it
> deviates from the "service standard" of calling
> TurbineServices.getInstance().getService(serviceName) and being returned an
> *instance* of a particular service on which you can call instance methods.
> If we are going to have a "service framework" then we need to comply with
> those specs.
>
> I'll look into it when I have more time.
My attempt at doing this static stuff was an attempt at taking the
Services stuff to the next level. I am complying with those specs, but I'm
also trying to expand on them a bit. I might not get it right the first
time, but I'm trying to show my thought process as I'm going...
I will fix the infinite loop tonight (unless you already fixed it).
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
