As you might have already read on www.ogre4j.org, it has been successfully generated! The bindings are still causing compile errors but that methods can be easily kicked out by hand. More than 90% of Ogre's API is available in Java now. We will fix the remaining problems and hopefully create a release soon.
We are happy to welcome ohhappyshen as new developer. With this backing we hope to get towards a release with big steps.
Since we use some of the tips Micheal Kay told us through the saxon-help mailinglist, the transformations are a lot faster. One of the unit tests, which we provided as example for the saxon community, runs about 3 times faster because of <xsl:strip-space/>.
We tried to run the transformations of the C code for OGRE on a AMD Athlon 3200+ and it took 3 days to terminate! Isn't this long? Friday evening after we applied the tips from Micheal Kay the build for the C code took 137 minutes. I think we are on the right path ...
I'm afraid I have bad news. After we made all unit tests running we tried to generate bindings for the complex API of the current OGRE release. We encountered a lot of errors and runtime problems. Additionally the execution of the XSL transformations are very slow because of some program mistakes and not cached xml queries. Now we are at a point where we need help of XSL freaks like Michael Kay ... So please XSL programmers out there help us!
The code for the automatic code generation of the C++/Java bindings to the 3D render engine OGRE (ogre4j) grew from three XSL transformation up to a complex build system with different technologies. XBiG was from the beginning designed as a generic tool which provides a framework to add XSLTs for more than CPP2Java. Now the time is come that XBiG got its own project page on sf.net. First commits to the SVN repository already done. Everybody is welcome to contribute to this project.