The Core team is now pushing harder than ever before toward the stable API for application code. A goal is to have this completed no later than mid-April, and hopefully, shortly after make an alpha release.
The Qi4j team is getting a lot of feedback, from visiting many companies, university and conferences the last few months. It has been interesting in many ways;
- People are impressed, confused and overwhelmed. All at the same time.
- People ask for "When are you going to release?"
- Big wish lists for web application frameworks, Swing framework, and so on.
- We get questions about integration with other wll-used technologies, such as Spring.
In reality, we are working as hard as we can, and the highest priority is to nail down everything that affects the client/domain code, a.k.a Core System API. We are also working with a few other key subsystems in parallel, with help from Edward Yakop, Alin Dreghiciu and Neo Technology AB;
- EntitySession management.
- SQL/RDBMS legacy integration support. How to make "rows" in existing SQL tables available as Composites in Qi4j.
- High-performance EntityStore, by integration with Neo4j
. - Mocking framework that is made specifically for Qi4j, to simplify mocking of Fragments.
- New and updated documentation on this site.
We are excited about future of this project, and everything is coming together soooo nicely.
Feel free to help out, making Qi4j the best thing since Java.