Thanks Edmond and Jochen for your reply.
I think the solution which Edmond is suggesting will be a hack not a proper
solution. Can someone from the dev mailing list answer a possible solution
for this problem.
Thanks
Harish
On Mon, Mar 20, 2017 at 5:26 AM, Edmond Kemokai wrote:
> Hi Harish,
>
Hi Harish,
You are right, the script name is just a somewhat random identifier. In
that case if you really must know the source file that caused the issue and
you are executing the groovy code, why don't you capture the resulting
exception and perhaps replace the Script.groovy with the name
of the
On 19.03.2017 17:29, Harish Dewan wrote:
Hi Edmond,
thanks for your reply.
the unique number which i was talking about is not the line number.
for example: below is an script exception thrown in case of syntax error.
I had introduced text 'abcd' in my hello.groovy script.
in case of exception it
Hi Edmond,
thanks for your reply.
the unique number which i was talking about is not the line number.
for example: below is an script exception thrown in case of syntax error.
I had introduced text 'abcd' in my hello.groovy script.
in case of exception it says below message
javax.script.ScriptExce
Hi Harish,
The should be the line number where the problem is. How are
you setting context that doesn't show file name? The code you're running
that has the error can't possibly extract something from the context since
there is an error (I am guessing syntax error?).
I am the developer of HiveMi
Hi All,
I am trying to run a groovy script from my Java code using JSR223 and I am
using 'groovy-all-2.4.9.jar' .
In case of any exception occurring, it gives a generic name as
Script.groovy , where as the script file name was
differently given.
I checked for possible solutions, like I need to set
