cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Foster <jafos...@uwaterloo.ca>
Subject Re: [status & RT] design challenges
Date Sat, 06 Apr 2002 15:56:20 GMT
> Workflow's approach appears to be based on a finite state machine
> model. Checkout the sample control file at:
>
> http://cvs.apache.org/viewcvs/jakarta-commons-
> sandbox/workflow/src/wizard-demo/WEB-INF/wizard.xml?rev=1.1&content-type=
> text/vnd.viewcvs-markup
>
> The same approach can be modeled in Cocoon today using actions.

Would it be possible to automatically transform a Workflow control file to 
a mountable sitemap using an XSLT stylesheet?  Sort of an "easy migration 
path" kind of thing.

Make you wonder if the same thing would be possible for something like JSP,
  ASP, and ColdFusion?  You'd think that a JSP->XSP converter would be a 
straightforward, simple transform.  ASP probably not because of language 
issues.  ColdFusion would be a little tricky, as you would have to emulate 
their custom language (JavaScript probably could do that if it had to), but 
is probably doable.

I realize that this could look like Flexibility Syndrome, but it would be 
*way cool* if Cocoon made it easy to adapt existing projects to the Sitemap/
Flowmap approach.  It's a great way to help people make the switch.

Jason


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message