Previously Jens Vagelpohl wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> On Mar 18, 2009, at 16:12 , Wichert Akkerman wrote:
> > Previously Miles wrote:
> >> We have quite a lot of copy-and-paste code here in order to support
> >> using a custom MemberData class for members in particular sites.
> >> The reason for this is that the only way to use a different
> >> MemberData
> >> class is to provide a custom wrapUser method.
> >> I'd like to propose that this is changed to use a factory registered
> >> through the CA to create new MemberData objects, in order that this
> >> is
> >> pluggable without requiring a custom MemberDataTool.
> > Can you explain the use case? I suspect you can also solve this with
> > PAS
> > and a custom user factory PAS plugin.
> One use case I have: I need a different Member Data object (and thus
> the whole overridden tool) for Products.CMFLDAP in order to have
> custom overridden methods on those MemberData objects that call non-
> standard methods on the user folder.
Personally I would rather find a way to get rid of the Member Data
object and rely PAS to provide all the required features. Is there
a reason, other than not wanting to add a dependency on PAS, to use a
Member Data object?
Wichert Akkerman <wich...@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
Zope-CMF maillist - Zope-CMF@lists.zope.org
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests