It is now better: the event DatabaseOpened is caught at startup.<br>
However, it is surprising that ProcessStartingEvent is not caught.<br>
<br>
Simon<br><br><div class="gmail_quote">On Mon, May 18, 2009 at 6:46 AM, Andreas Jung <span dir="ltr"><<a href="mailto:lists@zopyx.com">lists@zopyx.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 18.05.09 00:42, Simon Elbaz wrote:<br>
> Hi,<br>
> I am trying to execute some code at zope3 server startup. Zope3 posts<br>
> hint using a IProcessStartingEvent subscriber in configure.zcml.<br>
><br>
> Here is an extract of configure.zcml:<br>
><br>
> <subscriber<br>
> handler="cdcadama.authentication.onStartup"<br>
> for="zope.app.appsetup.interfaces.IProcessStartingEvent"<br>
> /><br>
><br>
> and the handler definition:<br>
><br>
> def onStartup(event):<br>
> print 'hello'<br>
><br>
> The problem is that the function is not called at server startup. But<br>
> when a call to notify(zope.app.appsetup.interfaces.ProcessStarting())<br>
> is made later in the code (after the server starts), it prints 'hello'.<br>
><br>
</div>Isn't there a DatabaseOpened event?<br>
<font color="#888888"><br>
-aj<br>
<br>
</font></blockquote></div><br>