I sincerely hope it never does. XML isn't worth "a pile of fetid dingo kidney" (TM) as a scripting language ;-).
What about XSLT, which has been proven to be Turing-compatible ?
The point is not whether the user can write a flow script in JAvaScript or XML. I don't want to use XML as a scripting language either. All that is needed is ability to define basic flows that don't involve significant logic beyond what can be done using JXPath using XML. Is that possible ?
Do you really think that any moron can script logic in XML using XMLSpy? Why not in Javascript, then?
Not any moron; only people who are fairly comfortable with things like XSLT.
you really find lots of developers familiar with it? Will you be able in the future? Learning the Woody markup can be done in a few hours, so
All right.
There are currently XForms books on the market (correct me if I am wrong, I believe an O'Reilly one just came out). Woody is not ready to be documented by a publisher yet.
XForms is more likely to be accepted by an XYZ MegaCorp in the U.S. than Woody/Cocoon Forms.
it's not that big deal, isn't it?
It is not a big deal to me personally. However, I had a hard time advocating XML at my previous project last year. The client was one of those American XYZ MegaBanks. 90% of the developers did not want to deal with learning more XML grammars than they should. They didn't even want to learn how to use custom JSP taglibs that I've written.
Antonio pointed out earlier that "From mid last year to today I needed to learn: Java, HTML, XHTML, CSS, XML, XSLT, POI, FOP, SVG, SITEMAP, XSP, XPATH, Javascript, OJB, JDO, Original DB Actions, Modular DB Actions, Forrest." There is a limit to how much a single person can learn, and the amount of time one is allowed to spend learning on the job is finite. The less to learn the better and more productive developers can be.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
