(Unlike the other scripting issues I've been reporting, this one is not causing my any problems at all, I just wanted to report this to get fixed during some idle moment - I think just adding "lang" to the cache key should fix it?)

I noticed this when trying to workaround the mvel bugs reported elsehwere (cough-hint-cough j/k). Here's the steps:

1] Run an mvel script that doesn't work in JS:

"script_fields":{
"test1":{
"script":"toRadians(0)",
}
},

2] Switch the language to JS

"script_fields":{
"test1":{
"script":"toRadians(0)",
"lang":"js"
}
},

This returns exactly the same response

3] Now make a trivial change to the script:

"script_fields":{
"test1":{
"script":"0+toRadians(0)",
"lang":"js"
}
},

This fails with the expected "EcmaError[ReferenceError: "toRadians" is not defined. (Script3.js#1)]" error

So it looks like in step [2] it's just re-submitted the original cached? mvel query

4] if I now change lang to be mvel, ie same script:

"script_fields":{
"test1":{
"script":"0+toRadians(0)",
"lang":"mvel"
}
},

It continues to fail, ie the (erroring) script has been cached.