Skip to main content

Which of the following would be more useful to you?

Calling a scripting language from Java
19% (148 votes)
Calling Java from a scripting language
20% (155 votes)
They'd be equally useful
42% (324 votes)
Neither would be useful to me
18% (140 votes)
Total votes: 767

Comments

Limiting the java scope

Some way of limiting the java methods that can be called from a script would be nice... ie: Say I'd like to export a set of classes and functions to be available to the script, but not allow the script to call just any method, make network connections, etc...

Limiting the java scope

Why does current access modifiers not enough to do the job?

The sum is greater than the parts

Java & JavaScript does a great job in strengthening each other's weaknesses - having 2-way interoperability between them is certainly vital.

In fact I would very much like to see E4X to be included in Mustang as rest of the Rhino implementation do - it just gives us so much flexibility and raw power when handling XML!

I use both all the time!

It really makes applications more useful to end users. Providing called scripts with a delivered application allows users to easily customise and extend the application's functionality. Similarly, providing details of how the application can be called from scripts allows customers to mix functionality of one application, with other scriptable applications. My particular favourite is BeanShell. It is extremely easy to use, especially for Java developers.