|
From: <jm...@so...> - 2001-12-20 21:29:36
|
On Thu, 20 Dec 2001, Daniele Tarini wrote:
> You are right, we skipped the 'client' parameter.
>
> The reason for keeping a 'client' parameter is not clear to me... is it f=
or
> your use or for Zope? I tried putting a document in the same folder the D=
TML
> is in, a property (with the same name, of course) both in OpenFlow and in=
the
> Process: what I got is that the referred item is the DTML in the same fol=
der
> the application DTML is in. So it seems that the context is the applicati=
on
> DTML parent. Isn't this the behaviour you wanted? I might have got someth=
ing
> wrong: do you mind explaining again?
>
> Maybe you are referring to the automatic start of application on an
> auto-start activity?
I am talking about this case:
- automatic activity
- the called method is acquired, outside the Openflow folder
- This method is a DTML-Method
- This method acquires something, in the way you expect (Zope acquisition,
it fetchs the methods, and the properties in the parent folder of the
DTML-methon, then in the parent of the parent folder... etc...).
What I had without the "client" parameter, was an error. While this method
worked in manual mode (calling it from the ToDoList), it failled in
automatic. I think that the DTML was acquiring from the Activity folder,
and that is why it failed.
Well, looking the Zope code, I setted "client" to the parent
folder, and it worked.
--=20
__o
_ \<_
(_)/(_)
Saludos de Juli=E1n
EA4ACL
-.-
|