> So, what about a general interface to flow controller (be it a flow script
> or a flow map) that will allow to use any implementation you like? I know,
> I've already ask about this before, just want to remind about it. And as
> I've already said, though, I like the idea of continuations very
> much, but I
> can't and don't want to use your JS-based implementation in our
> product, but
> would like to plugin our XML-based flow engine (it is also supports
> something like continuations - we call it 'history' here).
After a look into cocoon.xconf I think this is already possible:
<flow-interpreters default="JavaScript"
reload-scripts="true"
check-time="2000"
logger="flow">
<component-instance name="JavaScript"
class="org.apache.cocoon.components.flow.javascript.JavaScriptInterpreter">
<load-on-startup>resource://org/apache/cocoon/components/flow/javascript/sys
tem.js</load-on-startup>
</component-instance>
<!--
Temporarily disable Scheme, until full support is completed
-->
<!--
<component-instance name="Scheme"
class="org.apache.cocoon.components.flow.scheme.SchemeInterpreter">
<load-on-startup>resource://org/apache/cocoon/components/flow/scheme/system.
scm</load-on-startup>
<heap>/WEB-INF/sisc.heap</heap>
</component-instance>
-->
</flow-interpreters>
Regards,
Reinhard
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
