> With your code below, and with a concrete example, can you say what you
> want to happen, and what actually does happen?

> > Thus results in a url like this:
> >     /RequestTypes/<request type instance>/Task Templates/<task template
> > instance>,
> > and what I ideally want is:
> >     /RequestTypes/<request type instance>/<task template instance>.

Let's say I have a RequestType called "Evaluation of Product".  For this
request type I create Task Templates called "Record Customer Details" and
"Ship Product to Customer".  If I go to the Request Type "Evaluation of
Product" the url is: path.to.requestypes/evaluation_of_product.  This gives
me the detail of the request type as well as the list of task templates
relating to this request type.  If I now follow the link to the task
template "Record Customer Details", I simply want to click on a url that
says path.to.requesttypes/evaluation_of_product/record_customer_details and
do not explicitly want to go the TaskTemplates with

In other words, my traversal_method for the RequestTypes specialist should
first seek the object on it's own rack and if it can not find it is should
ask the nested TaskTemplates specialist for the object.


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

Reply via email to