Magn�s ��r Torfason wrote:
> 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.
Hey Magnus, this is not the proper way of solving the problem. I think
that it's the services that are misbehaving. When a service
calls setInit(true), no further initialization attempts will be made
(check BaseInitableBroker.java, lines 150 & 210). Some services
need both early and late initialization, therefore setInit(true) can
not be called in early initalization routines. Another flag can be
used by such service, to safeguard against double initialization.
Tell me which services are giving you trouble, and I can fix them.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
