Thread: Replace <Unknown Source> in EcmaError (JSR223) with actual file name

The file name, line number, and variable name info are included in the class files when compiled with the debug option -g. The JVM exception management can then pick them up from the class files at runtime to provide more informative messages. See Java Compiler Options.

Originally Posted by dlorde

The file name, line number, and variable name info are included in the class files when compiled with the debug option -g. The JVM exception management can then pick them up from the class files at runtime to provide more informative messages. See Java Compiler Options.

You must not be familiar with ScriptEngine. The files aren't compiled, their plain JavaScript files that are dynamically loaded and parsed. And that's not a compile error, thats a runtime error.

Originally Posted by Lord.Quackstar

You must not be familiar with ScriptEngine.

You're right, I'm not (well, not that familiar)...

The files aren't compiled, their plain JavaScript files that are dynamically loaded and parsed. And that's not a compile error, thats a runtime error.

I wasn't suggesting it was a compiler error, I was just saying that in order to get the filename and line number of Java source in exception messages, the javac -g debug options should be used when compiling Java source code. Clearly this will only tell you the last Java class file and line executed, not JavaScript innards, but I thought this was a Java question. If it doesn't apply here, then I'm sorry, it won't help

Any chance you can run your Javascript code in a normal browser by including it from a dummy HTML file, that way you could use the browsers Javascript debugger which is probably a lot better than your Java IDE

// Json

Originally Posted by Json

Any chance you can run your Javascript code in a normal browser by including it from a dummy HTML file, that way you could use the browsers Javascript debugger which is probably a lot better than your Java IDE

// Json

That would be probably the best way, but the issue though is that I also load util functions and place then at the top of the file (hence why its hard when an error like that shows up because I have no idea if its the util files or the command file).

And also this is java scripting, not browser scripting. Surly there's support for this since EcmaError has a spot for the file name.

Yes, point taken, I also think it should give you a nicer message than Unknown Source, is there anyway through the ScriptEngine you can set a debug flag of some kind?

I'm not too familiar with the ScriptEngine myself you see.

// Json