[Zope-CMF] Re: Five and CMFDefault

[David Pratt]

Hi Tres.  It was me.  Here is my trouble. I am am using CMFDefault in 
CMF-1.5.4 as a starting point for portal development. I have installed 
Zope 2.8.1 I have only modified main __init__ and Portal.py  at this 
point and done some renaming to reflect my portal product -but I am 
getting this error in my event log. I am not subclassing it since there 
are some fairly major things I will be doing but still will use some of 
what it there. I have done nothing to change any of the Five zcml or 
portal types yet so am puzzled why this is showing up. Can you shed 
some light as I am still in the dark when it comes to zcml.  I realize 
that these statements basically say it implementing inferfaces from 
CMFCore.

One thing I noticed is that there is no class 
Products.CMFCore.interfaces.IWorkflowDefinition. It is 
Products.CMFCore.interfaces.WorkflowDefinition  (no I in front of 
WorkflowDefinition).  Perhaps this is where it is getting messed up but 
why then is it not failing for CMFSite product? I upgraded my CMF 
yesterday but I have checked down to 1.5.2 and interfaces in CMF for 
types don't have I in front either but have same zcml as CMFDefault in 
1.5.4.  Was this something overlooked in CMFDefault or is it something 
I have done?  Let me know if you want the full traceback.

The traceback is because Five is refusing to load and I am interested 
in using Five for translation services in the new product.

Regards,
David

Last part of traceback:

     ConfigurationError: ('Invalid value for', 'interface', 'Module 
Products.CMFCore.interfaces has no global IWorkflowDefinition in 
Products.CMFCore.interfaces.IWorkflowDefinition')

This is where it is failing:

   <!-- DefaultWorkflow -->

   <implements
       class=".DefaultWorkflow.DefaultWorkflowDefinition"
       interface="Products.CMFCore.interfaces.IWorkflowDefinition"
       />

I have not changed interfaces file in the main portal product or 
DefaultWorkflow.  If I comment out this statement in implements file, 
it fails on the next statement in implements.zcml which is

   <!-- DiscussionItem -->

   <implements
       class=".DiscussionItem.DiscussionItem"
       interface="Products.CMFCore.interfaces.IDiscussionResponse"
       />

When I look at bridge, it seems also that bridge does not go from 
WorkflowDefinition to IWorkflowDefinition.

<configure
     xmlns="http://namespaces.zope.org/five"
     >

   <bridge
       zope2=".interfaces.Document.IDocument"
       package=".interfaces"
       name="IDocument"
       />

   <bridge
       zope2=".interfaces.Document.IMutableDocument"
       package=".interfaces"
       name="IMutableDocument"
       />

   <bridge
       zope2=".interfaces.portal_membership.portal_membership"
       package=".interfaces"
       name="IMembershipTool"
       />

</configure>



On Wednesday, October 12, 2005, at 11:42 AM, Tres Seaver wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Lennart Regebro wrote:
>
>> Not a Five problem, but a CMF problem, switching lists to 
>> zope-cmf at zope.org.
>>
>> On 10/12/05, David Pratt <fairwinds at eastlink.ca> wrote:
>>
>>> One thing I noticed is that there is no class
>>> Products.CMFCore.interfaces.IWorkflowDefinition. It is
>>> Products.CMFCore.interfaces.WorkflowDefinition  (no I in front of
>>> WorkflowDefinition).  Perhaps this is where it is getting messed up
>>
>>
>> Well, if you try to access
>> Products.CMFCore.interfaces.IWorkflowDefinition and it doesn't exist
>> you would get an error, yes. :) Besides, I have the feeling it should
>> be Products.CMFCore.interfaces.portal_workflow.WorkflowDefinition,
>> unless ther e is some magic going on. And I assume that the missing I
>> is just a typo.
>>
>>
>>> but why then is it not failing for CMFSite product?
>>
>>
>> It probably never arrives at using this?
>
> On the trunk, the "canonical" version of the interface is
> Products.CMFCore.interfaces.IWorkflowDefinition (defined in
> interfaces/_tool.py, imported into interfaces/__init__.py);  the Zope2
> version,
> 'Products.CMFCore.interfaces.portal_workflow.WorkflowDefinition', is
> created via a "reverse bridge" in interfaces/__init__.py.
>
> On the 1.5 branch, the canonical version is the Zope2 one,
> 'Products.CMFCore.interfaces.portal_workflow.WorkflowDefinition', with
> the Zope3 version created via a "forward bridge" in 'bridge.zcml'.
>
> HTH (I'm missing context to know whether this was a curiosity, or
> whether somebody saw an actual traceback),
>
>
> Tres.
> - --
> ===================================================================
> Tres Seaver          +1 202-558-7113          tseaver at palladion.com
> Palladion Software   "Excellence by Design"    http://palladion.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFDTSDL+gerLs4ltQ4RAkZwAKDNgx5QX+4DBX+gexruGLfxUOIJegCgn3mm
> rLtXBcG6uEHtEdQA/xuPTEw=
> =1RJP
> -----END PGP SIGNATURE-----
>
> _______________________________________________
> Zope-CMF maillist  -  Zope-CMF at lists.zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
>
> See http://collector.zope.org/CMF for bug reports and feature requests
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: text/enriched
Size: 5356 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope-cmf/attachments/20051012/845143c3/attachment-0001.bin