cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Andreas Hochsteger <>
Subject Re: Flows with Jelly as backend?
Date Sat, 15 Mar 2003 19:34:51 GMT
On Saturday 15 March 2003 13:56, Stefano Mazzocchi wrote:
> Andreas Hochsteger wrote:
> > Hi everybody!
> >
> > I wonder if anybody ever looked at jelly:
> >
> >
> > I found a hint to it in the Wyona/Lenya users mailing list.
> > It consists of an XML syntax and a tool wich interprets the XML documents
> > and it seems to be similar to the way ant works.
> >
> > Would it in your opinion make sense to support it as backend for Cocoon
> > flow like this is the case now for JavaScript?
> I would personally dislike this option because Jelly is rewriting a
> programming language using a markup language syntax, which is, IMHO, a
> very bad thing to do.

That's what I wanted to know, thanks.
Since I just discovered Jelly, I didn't know, if it's suitable for Cocoon.

> Moreover, it doesn't add continuation support so it could be no
> replacement for the flow, but just a different way to write actions.
> Interesting timing, BTW, as we are discussing the ability for people to
> plug new sitemap tags.
> Imagine having jelly inside the sitemap.
> Brrr, scary.

I have to agree ;-)

Is it generally acceptable to support XML-based process modelling 
standards in the future, which don't lead that easy to the misuse of flow 
functionality for things which should be better implemented in an other way?

Are there any requirements for such a language, which you can speak out 
(besides an implementation which supports continuations), to consider them 
for integration or support within Cocoon?

Here is an (incomplete) list of XML-based process/workflow modeling 
standards which are currently available or in development:
* BPEL4WS - Business Process Execution Language for Web Services (Bea,IBM,MS)
* BPML - Business Process Modeling Language (BPMI)
* ebBPSS - ebXML Business Process Specification Schema (
* PIP - Partner Interface Process (RossetaNet)
* UML - Unified Modeling Language (OMG)
* WSCL - Web Services Conversation Language (W3C)
* XPDL - XML Process Definition Language (WfMC)

Further information:
* XML-Based Workflow and Process Management Standards: XPDL, Wf-XML
* Still no universal workflow
* XML business-process model ready for release

Perhaps you can comment on them to help those, which don't have that deep 
knowledge of Cocoon internals, to better see the big picture about where 
Cocoon will go in the future.

Awaiting your comments,

	Andreas Hochsteger

View raw message