You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Carsten Ziegeler <cz...@apache.org> on 2005/10/10 16:57:48 UTC
[2.2] Bug in preloading/lazy loading
If you turn on lazy loading (currently the default), then components are
not preloaded even if the preload attribute is set to true.
Actually the evaluation of the flag works fine and the correct handler
is set, but no component is created as the handler is not initialized at
this stage.
For example, the hsqldb is not started on startup.
I'm not sure how to fix this. Perhaps by calling the initialize method
of the handler at some stage?
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [2.2] Bug in preloading/lazy loading
Posted by Carsten Ziegeler <cz...@apache.org>.
Carsten Ziegeler wrote:
> Sylvain Wallez wrote
>
>>
>>The only thing that could cause this it CoreServiceManager not being
>>called. But again, it works for me and I've explicitely seen this call
>>(checkout from mid-afternoon)
>>
>
> I'm using the latest SVN - I just tried it out on a different machine
> with a clean checkout - no difference.
>
> Now the really strange thing is that the CoreServiceManager seams to
> work correct. The check for the preload attribute in the
> getComponentHandler(...) method works and the correct component handler
> is called.
>
> I will try to find the difference between using lazy loading and not
> using it.
Even stranger - now it works, but it seems there is a problem with the
OJB initialization. The connection manager is not initialized. Ok, I'll
look into that in the next days. Lazy loading is working in general.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [2.2] Bug in preloading/lazy loading
Posted by Carsten Ziegeler <cz...@apache.org>.
Sylvain Wallez wrote
>
>
> The only thing that could cause this it CoreServiceManager not being
> called. But again, it works for me and I've explicitely seen this call
> (checkout from mid-afternoon)
>
I'm using the latest SVN - I just tried it out on a different machine
with a clean checkout - no difference.
Now the really strange thing is that the CoreServiceManager seams to
work correct. The check for the preload attribute in the
getComponentHandler(...) method works and the correct component handler
is called.
I will try to find the difference between using lazy loading and not
using it.
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [2.2] Bug in preloading/lazy loading
Posted by Sylvain Wallez <sy...@apache.org>.
Carsten Ziegeler wrote:
>Sylvain Wallez schrieb:
>
>
>>Carsten Ziegeler wrote:
>>
>>
>>
>>
>>>If you turn on lazy loading (currently the default), then components are
>>>not preloaded even if the preload attribute is set to true.
>>>
>>>Actually the evaluation of the flag works fine and the correct handler
>>>is set, but no component is created as the handler is not initialized at
>>>this stage.
>>>For example, the hsqldb is not started on startup.
>>>
>>>I'm not sure how to fix this. Perhaps by calling the initialize method
>>>of the handler at some stage?
>>>
>>>
>>>
>>Works for me... I even checked in the debugger, and see the Quartz and
>>HSQLDB threads running...
>>
>>
>Hmm, that's strange - I know it worked for me a long time ago, but
>currently it's not. Quartz does not come up, either. So any idea what
>the difference could be?
>
>
The only thing that could cause this it CoreServiceManager not being
called. But again, it works for me and I've explicitely seen this call
(checkout from mid-afternoon)
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director
Re: [2.2] Bug in preloading/lazy loading
Posted by Carsten Ziegeler <cz...@apache.org>.
Sylvain Wallez schrieb:
> Carsten Ziegeler wrote:
>
>
>>If you turn on lazy loading (currently the default), then components are
>>not preloaded even if the preload attribute is set to true.
>>
>>Actually the evaluation of the flag works fine and the correct handler
>>is set, but no component is created as the handler is not initialized at
>>this stage.
>>For example, the hsqldb is not started on startup.
>>
>>I'm not sure how to fix this. Perhaps by calling the initialize method
>>of the handler at some stage?
>>
>>
>
>
> Works for me... I even checked in the debugger, and see the Quartz and
> HSQLDB threads running...
>
Hmm, that's strange - I know it worked for me a long time ago, but
currently it's not. Quartz does not come up, either. So any idea what
the difference could be?
Carsten
--
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/
Re: [2.2] Bug in preloading/lazy loading
Posted by Sylvain Wallez <sy...@apache.org>.
Carsten Ziegeler wrote:
>If you turn on lazy loading (currently the default), then components are
>not preloaded even if the preload attribute is set to true.
>
>Actually the evaluation of the flag works fine and the correct handler
>is set, but no component is created as the handler is not initialized at
>this stage.
>For example, the hsqldb is not started on startup.
>
>I'm not sure how to fix this. Perhaps by calling the initialize method
>of the handler at some stage?
>
>
Works for me... I even checked in the debugger, and see the Quartz and
HSQLDB threads running...
Sylvain
--
Sylvain Wallez Anyware Technologies
http://people.apache.org/~sylvain http://www.anyware-tech.com
Apache Software Foundation Member Research & Technology Director