Comments on: Dynamic in-memory compilation

By: Ilya

Ilya — Wed, 17 Mar 2010 06:49:03 +0000

if you try to use that in a managed environment with non-default classloader (like j2ee container) you might run into problems, check out my article http://atamur.blogspot.com/2009/10/using-built-in-javacompiler-with-custom.html if that happens to you =)

By: Marin

Marin — Sun, 21 Feb 2010 11:44:28 +0000

In reply to Heinz Kabutz:
classLoader = MyOtherClass.class.getClassLoader();

By: Heinz Kabutz

Heinz Kabutz — Thu, 18 Feb 2010 17:01:00 +0000

Great article. Do you know how to get an existing classloader to define the new class? I don’t want to have to construct a new classloader for every new dynamic class that I am creating.

Should also work for the system classloader…

Heinz

P.S. I have found a way, but want to know if there is a better way

By: Marcus

Marcus — Wed, 06 Jan 2010 16:26:15 +0000

Great article, thanks! Google was returning me a bunch of articles that neglected explaining the ForwardingJavaFileManager subclass for accessing in-memory bytecode, so that was particularly helpful.

By: JavaBlogging » Scripting in Java

JavaBlogging » Scripting in Java — Mon, 30 Nov 2009 14:01:32 +0000

[...] article was inspired by a comment from Ricky on one of our previous post. [...]

By: Ricky

Ricky — Wed, 11 Nov 2009 17:03:13 +0000

interesting!

but about you conclusion, for evaluating math expression is simpler with the javax.script features… Like:

ScriptEngineManager mgr = new ScriptEngineManager();
ScriptEngine jsEngine = mgr.getEngineByName(”JavaScript”);
try {
jsEngine.eval(”print(2*2)”);
} catch (ScriptException ex) {
ex.printStackTrace();
}

By: software developers

software developers — Fri, 28 Aug 2009 12:18:32 +0000

Hey, that was interesting,

great coding skills, I learned a lot form you today

Thanks for writing about it