[groovy-dev] Scoping and trace backs
Rasmus Aveskogh <rasmus@...
2006-01-02 11:00:08 GMT
My company developes a provisioning application where the customer can
provide provisioning logics by writing scripts. The scripts are executed
within the application at runtine though the core engine written in Java.
Currently we have support for Beanshell and PHP but have glanced at Groovy
since the PHP integration uses proxy objects which isn't working well with
Hybernate, and Beanshell is a little strict when it comes to
Groovy seems to have everything in terms of object/class bridging which
PHP lacks, while also supplying a lot of "script candy" (Groovy SQL,
working with Maps and Lists etc).
We did a little proof of concept and found some blockers which I would
like to check with you as I know you're doing extensive work on the
Reference Implementation now.
First of all I know you're working on scoping issues, and during our tests
with JSR-4 there were some issues associated with odd scope behaviour. If
I reused a variable name in a totally different scope I ended up with
internal NPE's which is my very next question: Will there be better stack
Syntax errors and common errors are often easy to find, but every now and
then you end up with something like "Internal Error: NPE", which, in a
fairly large script is quite annoying. Beanshell would be a good role