You are probably informed that JavaFX builders are deprecated within Java 8 and will be removed from jfxrt.jar into Java 9.
The first time I saw ‘Builders’, I thought => “Oh, yet another dot-parenthesis bullshit !”. At this time I was reviewing JavaFX 2 beta API to replace our Flex stack, because we really needed multi-threading capabilities for managing complex and big data. (flex was still supported by Adobe…, and yes I’m a RIA fan :). It’s so easy to write cryptic and obfuscated code in ActionScript 3 + MXML.
But I gave them a try and thanks to amazing Eclipse formatter, I have found them nice and really convenient (less verbose and allowing imbrication).
When I read Michael‘s blog post about them [link here], I thought: “Yeah!!! these builders really rock !!”.
Only stupid developers never change their minds , no ?? :p
Today I want to share with you the newer JRebirth goal: Application Modularization
Please note that a new poll is published on the right bar related to this subject.
This teaser show Mastering Tables application (built with JRebirth Application Framework) run as an OSGI bundle into Equinox runtime (Eclipse’s OSGI framework) and for sure with Java 8 runtime.
Further developments will be made to improve integration (runtime & build) and to fix some small issues (like log localization failure).
No extra OSGI bundles have been used (only equinox and gogo console ones).
Let me know if you have any remark
Fatal error: Uncaught Error: Call to undefined function twentythirteen_paging_nav() in /homepages/14/d143909784/htdocs/jrebirth/blog/wp-content/themes/jrebirth/tag.php:33
#0 /homepages/14/d143909784/htdocs/jrebirth/blog/wp-includes/template-loader.php(74): include()
#1 /homepages/14/d143909784/htdocs/jrebirth/blog/wp-blog-header.php(19): require_once('/homepages/14/d...')
#2 /homepages/14/d143909784/htdocs/jrebirth/blog/index.php(17): require('/homepages/14/d...')
thrown in /homepages/14/d143909784/htdocs/jrebirth/blog/wp-content/themes/jrebirth/tag.php on line 33