Jens Vagelpohl wrote:
There's an outstanding issue in the collector about workflow scripts that are external methods. Currently, creating a snapshot of a site with external methods on the Scripts tab of a DCWorkflow will just blow up. The real question here is: Do we want to support that at all? Taking a quick look at the code two options come to mind:

- When extracting workflow script information, external methods are specifically ignored. The documentation is updated to reflect the fact that only DTMLMethods and Script (Python) (or items derived from them/behaving like them) are supported as far as import/export goes.

That would be enough for me.

- External methods gain support by extending the saved information to collect module/function values for external methods instead of trying to read the body. This *will* make an import blow up if the filesystem code the external method relies on is not in the expected location.

Yeah the problem is that external method's content is non-local.

I would favor the latter route, but would volunteer to implement either solution. What's the consensus? Or are there other alternatives?

I'm also ok with I/O of the external methods themselves, but I feel that's too much hassle. And it's not among my use cases.


Florent Guillaume, Nuxeo (Paris, France)   CTO, Director of R&D
+33 1 40 33 71 59   [EMAIL PROTECTED]
Zope-CMF maillist  -

See for bug reports and feature requests

Reply via email to