I personally find myself much more happy with javaflow, since compile time code checking is a must, and since i usually write flows that use a java backend, and it's much more simpler to use it directly in java than in _javascript_. This is expecially true if you have a complex backend (with polymorphism and/or other design patterns) where untyped _javascript_ (and the consequent rhino guesses) can cause hard to find bugs or even disasters. Also, quite commonly the backend and frontend are developed by different teams, with _javascript_ you have no way to check if a change in the backend can cause problems to frontend flows, while with javaflow automatic refactoring is applied also in flows, and backend guys can quickly check if they broke something. For anyone interested in the similarity between fowscript and javaflow, from a syntactic point of view, I came across this very good IBM tutorial which breaks things down into sitemap instantiation of classes, sitemap calls to methods (still via map:call function='method name"). Yo can view the article here: The only thing it didn't reveal is how to implement is how to implement var form = new Form("forms/artistOrder.xml"); form.showForm("artistLyricsPopUp1.xml",{"artistID":artistID}); var model = form.getModel(); var bizData = {"next" : model.next, "delItem" : model.delItem, "quantity" : model.quantity} Anyone? Andrew |
