Projects/Summer of Code/2007/Projects/KrossJava
Java backend for Kross
Kross is a scripting framework that allows a program to easily integrate support for multiple scripting languages. Currently Python, Ruby and KJS are supported.
This project aims to integrate Java as another supported scripting language. Java is among the most used programming languages according to various sources, so supporting Java in Kross opens a lot of potential for programs using Kross as a scripting backend. This affects among others popular applications as KOffice, KWord, KSpread, Krita, Kexi and SuperKaramba.
Create a Java backend for Kross. This will involve creating new code to the model of the existing modules for KJS, Python and Ruby. The code will have as much as possible (ideally full) documentation and unit test coverage.
Every application using Kross will transparently receive dynamic Java scripting support. Since Java is one of the major programming languages these days, it would allow lots of developers to start scripting with a familiar language.
Java comes with an extensive library of classes, which will then also be available to the program. Database access (JDBC), web server (Tomcat), RMI and networking, ... all become easily accessible for a wide variety of programs.
Developing happens in the KDE SVN. Basic things are starting to work while there stays still a lot of work.
Developing happens according to eXtreme Programming and the following list provides a basic list of some selected goals.
- [DONE] Get some basic code done, that links against the jvm.
- [DONE] Be able to run "kross Test.class" that does actualy execute some java code.
- [DONE] Integrate a custom classloader and put it into a kross.jar
- [DONE] Get a simple sample done to connect native methods from a QObject to a Java method.
- [DONE] Introduce Extension to wrap QObject's and add InvocationHandler to generalize calls.
- [ON PROGRESS] Java<=>Qt variables, quit a lot of them seem to be done already in the JVMVariant but we need to support at least the same set as the other bindings. But that's more a long time goal and shouldn't be that hard now where we have things in place already.
- [ON PROGRESS] Get that code generic to handle any kind of QObject. That point includes multiple sub-points.
- [TODO] Compile to bytecode on demand. Some code for this is in SVN, but it has lesser priority right now.
- [TODO] Provide a Kexi<=>HSQLDB implementation using the krossjava to have with it the first real world user: Kexi which is able to import/export to OO.org Base. This is a long time goal and absolute out-of-scope for this gsoc but remains defined as goal to provide an idea what the solution should be able to do and in what direction it may move.
- QtJambi integration...
- SUN Java 1.6 Bug #6493522 known for more then a year now :-/
- libjvm.so: cannot open shared object file: No such file or directory - we will dyn load it later anyway, so let's ignore it for now.
- since Java is more static then Python or Ruby, it's a tricky task to handle it in a dynamic way.
- rm -f CMakeCache.txt may help :)
- Dynamic Proxies are not flexible enough. See r685415.