In most instances the REQUEST should be all you ever need. You can safely
pass a REQUEST as second parameter to a DTML Method (most of the time).

If you *really* want to be called with a namespace the preferred
way is to derive your class from Shared.DC.Scripts.Bindings.

Also see <>


On Fri, 3 Jan 2003, Bjorn Stabell wrote:
> I have two functions, PlainFunc and DTMLFunc, where PlainFunc is Python
> method in a file system product, and DTMLFunc is a DTML Method in the
> What I want to do is this:
>     ZPublisher calls PlainFunc (publishes it)
>     PlainFunc calls DTMLFunc
> in such a way that DTMLFunc gets everything it needs, e.g., namespace,
> but PlainFunc can do funky things to this namespace before-hand (like
> insert a few variables into it).  In other words, I want a Python method
> to wrap around a DTML method.
> I've encountered many problems caused by the awkward calling conventions
> for DTML methods and the automagic switching between different calling
> conventions by the ZPublisher (isDocTemp; can I set that for a normal
> Python method?).  Right now, I'm struggeling because I cannot get the
> namespace to be passed to PlainFunc, therefore PlainFunc cannot pass the
> namespace on to DTMLFunc.  Any clues?

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to