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.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
