[Zope3-dev] ISourceQueriables / Bug

Roger Ineichen dev at projekt01.ch
Wed Feb 9 04:50:35 EST 2005


Hi jim,

> -----Original Message-----
> From: Jim Fulton [mailto:jim at zope.com] 
> Sent: Tuesday, February 08, 2005 5:38 PM
> To: dev at projekt01.ch
> Cc: zope3-dev at zope.org
> Subject: Re: [Zope3-dev] ISourceQueriables / Bug
> 
> Roger Ineichen wrote:
> > Hi together,
> > 
> > There is a bug in the vocabulary 'PrincipalSource' 
> > method 'getQueriables' or somewhere around this lookup.
> > 
> > Usecase:
> > 
> > in the root ++etc++site:
> > - Add PlugableAuhtenticationUtility
> > - Add GroupFolder
> > - Add Principals
> > - Edit PAU for useing group folder and principal
> > 
> > in a subsite ++etc++site:
> > - Add a folder below the root.
> > - Make the folder to a site (Mekt site)
> > - Add PlugableAuhtenticationUtility
> > - Add GroupFolder
> > - Add Principals
> > - Edit PAU for useing group folder and principal
> > 
> > If you now go to the subsite's grant.html
> > view you see all the sources.
> > 
> > The groupfolder of the (root) site doesn't show up.
> > Instead of this source we I get the groupfolder
> > of the subsite twice.
> > 
> > The reason why, I used the same prefix and name
> > for the gorup folders.
> 
> This sounds like a bug.  I don't have time to look at it now.
> I suggest creating a collextor entry, preferably with a
> functional test.
> 
> > Can we:
> > a.) disallow to use the same prefix twice
> 
> No, there are specialized cases where you need to do this.

That's fine.

> I realy don't see, however, why the prefix should affect
> searching.

What does call the next source the the context if I have 
to same named GroupFolder utilities?

Is it the method getUtilitiesFor if I have two named utilities
'groups'?

like:
the getUtilitiesFor(IGrouFolder, 'groups')

If so, we should filter the result of getUtilities for
of duplicated named utilitites. Right?

I think it's in the vocabulary 'PrincipalSource'. Right?

> > or
> > b.) don't give the same named group folder (source) back twice.
> 
> Yes, we should be able to arrange to fix this.

Ok, let's do it. (b.)
Should I start do fix it? Or are you working on it?


Regards
Roger Ineichen

> Jim
> 
> -- 
> Jim Fulton           mailto:jim at zope.com       Python Powered!
> CTO                  (540) 361-1714            http://www.python.org
> Zope Corporation     http://www.zope.com       http://www.zope.org
> 



More information about the Zope3-dev mailing list