cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marco Rolappe" <>
Subject AW: Where is disposed called for the Stores?
Date Wed, 14 Apr 2004 23:42:09 GMT
hi corin,

the container is responsible for dispose()ing the components (which for this
to work have to implement avalon framework's Disposable, of course).

I'd suggest to set method entry breakpoints for the store's lifecycle
methods and look what's happening (e.g. maybe an exception thrown during
store's dispose).

> -----Ursprungliche Nachricht-----
> Von:
> []Im Auftrag
> von Corin Moss
> Gesendet: Donnerstag, 15. April 2004 00:58
> An:
> Betreff: Where is disposed called for the Stores?
> Hi Guys,
> I'm trying to integrate some of the new JCS improvements into our JCS
> based store.  The biggest one is a fix to the "shutdown bug" which
> ensures that the memory based key is written out to disk at shutdown
> time.  At first I thought that the dispose() method of AbstractJCSStore
> was being called, I'm now sure that it isn't.  In order for normal
> shutdown procedures to happen this method must be called.
> What exactly is supposed to invoke this method? Specifically at
> shutdown, I've not been able to find anything which does.
> Anyone got any insight?
> Thanks,
> Corin
> ================================================================
> CAUTION: This e-mail and any attachment(s) contains information
> that is intended to be read only by the named recipient(s). It
> may contain information that is confidential, proprietary or the
> subject of legal privilege. This information is not to be used by
> any other person and/or organisation. If you are not the intended
> recipient, please advise us immediately and delete this e-mail
> from your system. Do not use any information contained in it.
> ================================================================
> For more information on the Television New Zealand Group, visit
> us online at
> ================================================================

View raw message