Re: zope.component.zcml and global registry

"Roger" <[email protected]>
Newsgroups gmane.comp.web.zope.devel
Message-ID <201003090147497.SM01240@mobile05>
Hi Hanno 

> Betreff: Re: [Zope-dev] zope.component.zcml and global registry
> 
> On Mon, Mar 8, 2010 at 7:23 PM, Roger <[email protected]> wrote:
> > Another point, reloading ZCML actions after a system 
> startup e.g. from 
> > the UI is probably not possible anymore. Then we whould 
> have to call 
> > setSite(None) and this, on a running system, whould force 
> to loose the 
> > local components registry at the same time.
> 
> I'm not sure if there's other code that implements this, but 
> if you look at the way I do it in plone.reload [1], you'll 
> notice that it already does an explicit getGlobalSiteManager 
> call and a setSite(None). The site is set again on the next 
> request, when traversing over the local site object. The code 
> also has to minimize the ZODB cache, or the local site will 
> have some cached info that might have been invalidated by the 
> global changes.
> 
> So I don't see this as a counter argument :)

There is allways a way to do things ;-) Tweak a running
system itself for reload configuration is probably not the
best one.

As more as I think about what Fabio changed and what really
happens, I think it's just a missing API which splits the
ZCML action configuration and the running system into
different parts.

But since you're telling that reload patterns can work with 
this changes, I think this is good news.

Regards
Roger Ineichen

> Hanno
> 
> [1] 
> http://svn.plone.org/svn/plone/plone.reload/trunk/plone/reload/zcml.py
> 

_______________________________________________
Zope-Dev maillist  -  [email protected]
https://mail.zope.org/mailman/listinfo/zope-dev
**  No cross posts or HTML encoding!  **
(Related lists - 
 https://mail.zope.org/mailman/listinfo/zope-announce
 https://mail.zope.org/mailman/listinfo/zope )
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.