Re: O-XML translation to Java
Sincere apologies for not answering this earlier, it somehow got lost
in the pile.
Due to fundamental differences between Java and o:XML, such as static
vs dynamic typing and the pervasive use of XPath in o:XML,
translation is somewhat complicated.
A good while ago I did a proof of concept code translation that uses
XSLT to produce Java code which can then be compiled against the
ObjectBox libraries. It was never completed to implement all language
features, but showed that it can be done. (Let me know if you want to
try it out)
Since then efforts have focused on the Java-based interpreter, which
achieves comparable performance to the translated code and is much
easier to use. Debugging code that's been translated then compiled is
Longer term plans include developing the MLML  concepts to build
Java and/or .Net byte-code generators, thus circumventing the need
for generating Java sources. In effect, the o:XML compiler _is_ a
translator that produces an abstract syntax tree, which can be fed to
either an interpreter or code generator.
hope this answers your question, again, sorry for the tardy response!