I have the following weird requirement.
I am given:
- A list of some method names.
- Names and types of parameters of the above methods.
- The functionality of the above methods. This is as follows:
For each parameter, the method converts it to string using
toString
and obtains an array of strings. To this array, the method applies a functionfoo
. The functionfoo
takes as input aString []
type and outputsString
. The methods return whatfoo
returns.foo
's code is given inside a Java object and is to be accessed as a black-box.
The info in 1. and 2. can be in a text or XML file. For this purpose, we can consider it to be available inside a Java object in whatever way we choose.
The task is to create a .class
file (i.e., bytecode) that implements those methods and can be run on the JVM.
I think this assembler library would be one way to do it. Can anyone suggest an easier way?
[EDIT:] I can think of one other way: first generate the .java
file and then compile it to get the .class
file.
[The context:] I have to do this for several hundreds of methods. I want the shortcut so I can automate my job rather than manually write the code.
Here is a list of Open Source ByteCode Libraries: http://java-source.net/open-source/bytecode-libraries
Have a look at Javassist.
You could generate the required program code in Java syntax and turn it into a class file using the compiler. It's possible to instantiate
javac
at run time and pass it a byte array instead of the location of the source file. This is probably the easiest for other programmers to maintain.If you want to generate byte code directly, asm is the library most commonly used.
I saw you answer to my comment, but it is still not clear for me why you want to generate the code to be then packaged in a jar, just type it :)
Now if you want a typesafe api with all method having the same behaviour you could provide a dynamic proxy for a given interface (this leaves you with the question on how to generate the interface :)
Here is an example where all the calls to all the MyInterface method will be handled by the invoke method (just add methods to the interface to test it)...