2

It seems to me that the Java Compiler API allows to compile at runtime a class, writing its output (the .class file) to the file system. However, in-memory compilation is not supported. Is this correct ? or is possible to use this API to compile a class in memory (from a String) and instantiating such class afterwards ?

(I know I can compile the class to the file system and load it afterwards with a custom class loader, but I am wondering if I can compile it in memory, without passing by the file system).

Is there another alternative mechanism to do such in memory compilation using the J2SE only? BeanShell (I library that can do what I want) mentions in its web page that it may be included in the J2SE at "some point in the future", however, the status of its JSR is "Dormant" (whatever does it mean).

Update:

Ideally, I would like to know if this can be done with the J2SE only (or if there are any expected enhancements to J2SE that will allow me to do this in, for example, Java 8). However, tips about how to do that requirying the JDK to be installed are also appreciated (thanks Evgeniy).

Sergio
  • 8,532
  • 11
  • 52
  • 94

3 Answers3

4

It is possible if you have JDK, java complier is in tools.jar which comes with JDK only. See http://docs.oracle.com/javase/7/docs/api/javax/tools/package-summary.html

Evgeniy Dorofeev
  • 133,369
  • 30
  • 199
  • 275
  • but I do not need the JDK for just using the Java Compiler API, right ? – Sergio Sep 22 '13 at 16:37
  • right, but ToolProvider.getSystemJavaCompiler(); will return null then – Evgeniy Dorofeev Sep 22 '13 at 16:38
  • I see, but you think it would allow me to do the in memory compilation that I need, correct ? Are you aware of licensing issues I should take into consideration ? Probably the JDK is more restricted than the J2SE. – Sergio Sep 22 '13 at 16:43
  • 1) http://www.java2s.com/Code/Java/JDK-6/CompilingfromMemory.htm 2) I am 100% sure there's no licencing issues – Evgeniy Dorofeev Sep 22 '13 at 16:46
  • 1
    You need something _implementing_ the Java Compiler API. If you do not drag in e.g. the Eclipse compiler in a jar, you need the JDK to provide the compiler in javac. – Thorbjørn Ravn Andersen Sep 22 '13 at 17:04
1

Java Compiler API .. in-memory compilation is not supported. Is this correct?

No. The STBC uses the JavaCompiler to do exactly that.

..and instantiating such class afterwards?

The STBC does not go as far as trying to load/run the class, but I believe it should be possible. I imagine it might require a custom 'in memory' class loader though.

..the JavaCompiler API can do that independently if the JDK is installed or not?

From the page..

System Requirements

STBC will run on any computer with a version 1.6+ Java Plug-In* JDK (AKA SDK).

* The API that STBC uses is merely a public interface to the compiler in the tools.jar that is distributed only with JDKs (though the 'public JRE' of the JDK also seems to acquire a tools.jar). ..

Community
  • 1
  • 1
Andrew Thompson
  • 168,117
  • 40
  • 217
  • 433
  • I am a bit confussed, the JavaCompiler API can do that independently if the JDK is installed or not ? (as Evgeniy said ?) – Sergio Sep 22 '13 at 17:06
  • 1
    Please make your answers self standing. Answers on the form "please read the whole documentation to my pet project" have room for improvement. – Thorbjørn Ravn Andersen Sep 22 '13 at 19:06
  • @ThorbjørnRavnAndersen The answer was edited to include the relevant part, soon after I made that (now deleted) comment. – Andrew Thompson Sep 22 '13 at 19:19
1

JeKa (https://jeka.dev) provides a rich set of class to make it simpler than using JdkTool.

jerome angibaud
  • 41
  • 2