Hi Sören,
Interesting approach - having something that will be able to track more
easily the evolution of the Jena codebase is great to see. There seem
to have been an increase in questions on StackOverflow and on
answer.semanticweb about Jena on Android over the last few months so
great timing.
Is there are anything the Jena project can do that would make the
conversion? There may be things that Jena does, or the way is it
packaged, that are inconvenient for you but really make no differnce to
the project - sometimes things are just the way they are because it was
done that way but could easily be done another way. If you have any
such points, do email thsilist or raise a JIRA.
On Android, how does TDB work well? TDB uses fairly traditional file
handling for 32 bit machines - "direct mode" - and uses memory mapped
I/O for 64 bit machines - "mapped mode" - if it can detect the mode
correctly. Detection is not subtle, it looks in system property
"java.vm.info" and default to 32 bit. In mapped mode, it does try to
use as much memory as possible which is not friendly to co-resident apps
(you can force "direct" mode programmatically).
Andy
On 03/03/15 13:28, Sören Brunk wrote:
Hi all,
We are working on some Android app prototypes that deal with RDF data.
To make things easier, we have created a version of Apache Jena that
runs on Android. It basically consists of a bunch of Maven build files
that do some repackaging of the original Jena jars in order to make them
run on Android's Dalvik VM. As the port might be interesting to others,
we have published it to Github for everyone to use.
From the project description:
This project aims to make the Apache Jena Framework usable on Android.
While Jena is written in pure Java, it can't be used on Android as is,
due to multiple package conflict issues. To overcome these issues, we
have created an Android port enabling developers to use Apache Jena in
Android apps. In contrast to other ports we don't just publish binaries,
but make the Maven build files of the port available. We also stay as
close as possible to the original (i.e. no source code changes). This
should make it easier to stay in sync with upcoming Jena releases.
The project, including usage instructions, is available here:
https://github.com/seus-inf/jena-android
See here for an older discussion about the issues:
http://mail-archives.apache.org/mod_mbox/jena-dev/201304.mbox/%3C5163E9A0.2030307%40apache.org%3E
Best regards,
Sören
