On Mon, 2009-01-12 at 22:05 +0100, Martijn Faassen wrote:

> Okay, I'll take another look then and look at ObjectRef. Ah, yes, Dan 
> pointed out to you that you are using a zope.schema.Field in a class 
> instead of in a schema (an interface). That isn't right, and since the 
> direct use of that causes an error, that looks suspicious. Whether it is 
> the cause of the bug or not I do not know.

Thanks to all for the help.  
I will put together a wiki page that chronicles and explains the entire
issue and process of getting here. Along with the simplest example I can
come up with.

I'm still a little confused about why using Field as a base class is
wrong.  I know that it wasn't it's original purpose but here is the

I originally inherited from 'object' in my base classes and from
Interface in their associated interfaces.

But, because many of the base classes (and their schemas) are required
to define attributes of other classes. I  found that I did not have the
meta-data attributes such as required, default, etc for those schemas to
represent the attributes in the latter schemas.  So I chose to inherit
from IField and Field in my bases so that I inherited.  

Now maybe there is a MUCH more appropriate way to build these OSHIP base
classes than inheriting from Field.  But in mid-2007 I searched hi and
lo and asked on the mailing lists and still do not have a better

So if someone can tell me where I can find the documentation/examples
for building your own schemas that will be validated then I'll re-factor
the entire application to make it right.


<<attachment: oe_trick.png>>

Attachment: signature.asc
Description: This is a digitally signed message part

Zope-Dev maillist  -  Zope-Dev@zope.org
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to