Sundararajan's Weblog

  • Java
    January 3, 2008

Latest on the Scripting project

Guest Author
Updates on the Scripting project.

  1. Updated JavaScript script engine with Rhino version 1.6R7. This version supports E4X without requiring XMLBeans.
  2. Updated Groovy script engine to use version 1.5.1.
  3. Updated Jython script engine to use version 2.2.1.
  4. Updated Freemarker script engine to use version 2.3.11.
  5. Yoko Harada is planning to update JRuby script engine with version 1.1x.

Join the discussion

Comments ( 3 )
  • Rahul Roy Thursday, January 10, 2008

    Hey Sundararajan,

    Looking at that E4X link in your post, i started missing my days when i used to play a lot with XQuery; it looked much similar. I wonder if this could be considered as an alternative to XSLT; what's your view?



  • A. Sundararajan Thursday, January 10, 2008

    Hi Rahul: do you mean XQuery being similar to XSLT? Yes, those are similar. But, I like XSLT -- because of functional nature. Did you look at XSLT 2.0 implementation (say, Saxon)? If you are talking about E4X, I'm not terribly excited about it. Yes, it is easy to use (and misuse!) at times. In general, I am not comfortable with XML literals creeping into programming languages - be it JavaScript or Java or any language. But, some people seem to like it. In a sense, it is like embedding SQL with procedural/object oriented programs (remember Pro\*C?, SQLJ?). I didn't like that either. May be, it is just a matter of taste? I'd rather stick to XSLT/XPath rather than moving to E4X or XQuery.

  • Rahul Roy Friday, January 11, 2008

    Hey Sundar : I play around a lot with generating sources from XML definations and have for long used XSLT for the purpose. When I looked at E4X, I could see a potential in it to replace XSLT. I also did a prototype to confirm this thought; and you would be amazed to know that the E4X thing not only scaled to the expectations but the source was much understandable, as in readable, thus easy to maintain as well.

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.