I've experienced a dangerous behaviour with namechoosers :

If the namechooser computes a name which is the same as the current name,
the object is deleted!

This is simple to reproduce :
- register a name chooser that only returns "foobar"
- create your object → ok it's name is foobar
- from the Contents view of it's container, try to rename it (with a different 
- → deleted

Someone should try to reproduce that, to be sure that's not a side effect of my app, but I don't think so.

Zope3-dev mailing list
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to