Re: [Zope-dev] Re: [ZODB-Dev] Reloading product in 2.8
Shane Hathaway wrote at 2005-7-18 16:46 -0600: ... 3. If you want to refresh a product that registers itself with another product, you have to set up dependencies like in step #2. When you want to refresh, you have to refresh the product that contains the registry, not your own product. Otherwise the registry will refer to instances of the old product classes. I think when the product with the registry behaves like this (i.e. it keeps the old entries rather than takes the newly registered ones) this product does something wrong. The best way would be to fix this product... Otherwise (just to be explicit about this), you need to refresh both products: the one with the registry and the registering product. -- Dieter ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: [ZODB-Dev] Reloading product in 2.8
On 7/15/05, Shane Hathaway [EMAIL PROTECTED] wrote: Indeed, it does work for some people, but I've personally witnessed some very intelligent folks spending hours on problems created by misuse of Refresh. Maybe this is attributable to documentation. could be, because i have now, for several years constantly heard th statement that it works if used correclt, but nobody can tell me what correctly is... Hence, for me it has been useless even since it became part of core. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: [ZODB-Dev] Reloading product in 2.8
[switching to zope-dev] Sidnei da Silva wrote: On Fri, Jul 15, 2005 at 07:49:10PM +0200, Dieter Maurer wrote: | But, it does not need to fail -- provided that with a product | all its dependent products are refreshed as well. | | At least, I never saw it failing when I had met this condition... | | And I lost time only when I saw the not very helpful problem messages | for the first few times (when I did not met this condition). | | But otherwise, refresh saved me *lots* of time... Same here. If you know the gotchas and you program properly it can work flawleslly. Hell, I've even been able to refresh Archetypes products, what can be more prone to fail than that? Indeed, it does work for some people, but I've personally witnessed some very intelligent folks spending hours on problems created by misuse of Refresh. Maybe this is attributable to documentation. At the time Refresh was created, Zope products were generally simpler and didn't have any run-time registries. Refresh is now less reliable mainly because products are more sophisticated. Shane ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
