on 12/6/2000 11:06 AM, "Magn�s ��r Torfason" <[EMAIL PROTECTED]> wrote:
> Jon, I know that you are (understandably) wary of patching or otherwise
> meddling with Turbine.java, but I have a problem that I can not see how to
> solve with other means.
>
> I'm using Rafal's TurbineConfig class to init turbine without a Servlet
> runner. It is working great, but my problem is that my system may be fired
> up with a WebService running, or without it.
>
> This causes Services to be initialized twice (first with Rafal's code, and
> then on the first hit to the Turbine Servlet), causing most of the services
> to scream in pain, since they do not expect double initialization.
>
> What I did was put a firstInit variable in Turbine servlet, comparable to
> firstDoGet.
>
> The overhead is nil, since the code is run only once, and I hope the minimal
> code bloat is acceptable (or that a better solution exists).
>
> Magnus
I'm +1 on this patch, but I'm -1 on your coding style. :-)
I will get this checked in.
Also, anyone know why the scheduler is initialized in there as well?
Shouldn't the Services API be initializing it?
-jon
--
Honk if you love peace and quiet.
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
