Berin Loritsch <[EMAIL PROTECTED]> writes:
>Henning P. Schmiedehausen wrote:
>> So this looks like some sort of "lazy init" to me, which is fine, but
>> bites the Torque/Turbine folks, because the access to the component
>> happens via a 'bypass' with static facade classes and not directly
>> through the Avalon Component (yes, it's a design error and it's ugly
>> but it is how it is and it will be fixed in a later version of Torque
>> but we can't do this right now).
>>
>> Is there any way to get 'around' this lazy init? I'd like to get the
>> TorqueComponent initialized and started right when the container is
>> initialized. Is this possible with another container?
>If it is ThreadSafe, it should start up right away. If it is pooled,
>there is no way around it.
Hi,
I used
public class TorqueComponent
extends AbstractLogEnabled
implements Component,
Configurable,
Initializable,
Contextualizable,
Startable,
ThreadSafe
{
...
}
No, it does not start immediately. Only when the component is
requested for the first time. At least with ECM.
Regards
Henning
--
Dipl.-Inf. (Univ.) Henning P. Schmiedehausen INTERMETA GmbH
[EMAIL PROTECTED] +49 9131 50 654 0 http://www.intermeta.de/
Java, perl, Solaris, Linux, xSP Consulting, Web Services
freelance consultant -- Jakarta Turbine Development -- hero for hire
--- Quote of the week: "It is pointless to tell people anything when
you know that they won't process the message." --- Jonathan Revusky
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
