I’ve been working on a piece of software for some time now that is almost ready for a public release. For part of it I needed to connect to various databases, some of which are only accessible via JDBC. My problem is that my app is written in Objective-C. For the first version of my app this wasn’t a problem as Apple was promoting their brand new Objective-C to Java bridge and everything worked really nicely. That was until a couple of years ago when Apple decided to deprecate the Java bridge. I rewrote that code to use JNI and all was good. Then Apple brought out the Mac App store but announced that it would not accept any apps that link directly to the JVM. This causes a problem for me as without the JDBC drivers the usefulness of my app is greatly reduced.
I looked into various ways of embedding the JVM into my app, but the problem with doing that was that it increased my app from less than 10Mb to around 100Mb. I wasn’t too happy about that to say the least, so I looked into providing a way to make my app optionally use the system JVM allowing the Java support to be turned off. This worked pretty well unless the machine didn’t have a JVM installed in which case my app would refuse to load due to linkage failures. So, I had the bright idea to use Apples “new” XPC feature. I reorganised my JNI code to allow it to be called from an XPC process and found that the security settings meant that the JVM could not access any of the JDBC driver files in my app bundle. I got around that by using a folder shared with a process group. This allows the JDBC drivers to be loaded, but then I found that for some reason the JNI code that had been running very nicely for a couple of years didn’t like running inside an XPC process and would fail randomly with strange errors. On top of that I found that the process of going from Java, through JNI to Objective-C, then from the XPC process over to the main app was very slow and was especially noticeable with some of my larger data sets.
In desperation I decided to abandon the JNI code altogether and see if I could communicate from the main app to the java code in some other way. In the end I created a Java JDBC connector that communicates with the main app via a pair of Unix pipes. I have found this to amazingly fast and extremely reliable. Instead of the data going through several transformations from Java, through to JNI and then to Objective-C and so on it now goes directly from the Java code in a special serialised format directly into the Objective-C code via the pipes. It works really well