A POC (proof of Concept) is being written to explain how to build a JRebirth based application that communicate with a JEE server. As usual it gives me a lot of ideas to improve some parts of JRebirth (ie: adding default CRUD support) API, I will work some weeks on it, let me know if you have more urgent tasks.
Obviously this application will be open sourced, it will deal with a subject that will interest a lot of fan of a certain hexalogy (and more)…, I’ve just hired an assistant: my elder son who knows a lot of fine details about the saga. Check the JRebirth Github pages to be informed of work progression.
The architecture used will be quite simple to be easily customizable and reusable in other contexts.
Servlet Container: Tomcat
Database Access Layer: JPA => Hibernate
Communication Layer: JAX-RS => Jersey
Serialization Engine: JAX-B
Client Framework: JRebirth 😉
Later I will probably extract some files to build a more complex Maven archetype (client-server), give me feedbacks if you are interested in.
I haven’t blog for a while because I had to prepare a special coming (not arrived yet).
You have probably heared that a JSR has been started to normalize JavaFX Application Framework: JSR 377 Desktop|Embedded Application API.
I have made a summary of which features are supported into JRebirth.
As you probably know JRebirth has a powerful thread engine that kick away all coding complexity that could lead to User Interface corruptions, lags or the worst one a totally frozen interface.
It’s really difficult to create dynamically a lot of threads without adding some bugs to the application. JRebirth provides a powerful way to simplify your developments.
With the advent of Java 8 (with Method References) and JRebirth 8, it’s now possible to chain and combine Tasks running into specific Thread in a very convenient way.