Looks like the next release of Java will have support for Javascript built-in:
Another language-related JSR planned for Mustang is JSR 223. This defines a framework to allow scripting language programs to access information developed in the Java platform. We currently plan to integrate this into Mustang for b40. Aside from the framework, we will also include a JavaScript engine based on the Mozilla Rhino implementation. Later, we hope to include a scripting shell that is script language independent. This will be a very cool way to create a prototype, do some exploratory coding, and learn new APIs.
This is incredibly important for Cocoon, whose Flowscript is currently based on Mozilla’s Rhino Javascript interpreter. Actually, the Flowscript is somewhat language agnostic, but the only working implementation right now is in Javascript.
In the past there have been doubts concerning the viability of Rhino and its licensing terms, but when it’s become an integral part of the J2SE platforms, there will be no more doubts.
Now the question is: How long will it take to add continuations support to Groovy, so that developers will be able to choose between two great scripting languages for their flowscripts?
(Via Dion.)
Someone ever shown interest in continuations for groovy?
I think a better bet would be asking when #callcc would be implemented in JRuby since ruby-the-language already has that
Rhino is “the only working [flowscript] implementation right now”?
Hey Ugo, we also have JavaFlow (continuations in pure Java) and the less known Apples (weird name BTW) which is heavily used by the Daisy CMS!
I was under the impression that Javaflow wasn’t as stable as Javascript Flow, but this is probably due to my not having followed its development closely of late.