One thing most programmers hate is to write boilerplate code. Endless hours are spent setting up entity classes and configuring database connections. To avoid this you can let a program like Speedment Open Source generate all this code for you. This makes it easy to get a database project up and running with minimal manual labour, but how do you maintain control of the written code when large parts of it is handed over to a machine?
Say that you have a database with a table "user" which has a column "gender", and you want that implemented as an enum in java. If you run Speedment and use it to generate code, the "gender" field will be represented as a String. The reason for this is that there isn’t any built-in mappers for converting between database ENUMs and custom java classes. This is one of those cases when you might feel that the generator is taking away control for you. Well, fear not, for since the 2.3 Hamilton release, you can get this same control by creating your own plugin for Speedment!
Since Java 8 has been launched almost two years ago, it has been gaining more and more traction around the community. Most Java frameworks and platforms have either already migrated their APIs to Java 8, or are planning to do so.
With our latest update, the whole IntelliJ Platform has migrated to Java 8, which has allowed both ourselves and plugin developers to use the new language features. Among other reasons, this motivates us to further improve our coding assistance to make it more friendly to Java 8.
The long-awaited moment has come, and now we are happy to announce that the CUBA Platform has finally joined the free software community! From now on, the runtime part of the platform is open source and distributed under the Apache 2.0 license. This means that you will be able to create and distribute your applications for free! So, go ahead and start your CUBA application right now!
In this post, I would like to highlight why and how we have changed the licensing track.
Over the past few weeks, we’ve been working with the teams at Xamarin and Microsoft to assess the technology and business conditions of RoboVM to determine the path forward for the products. After looking at the complete landscape for mobile development with Java, the decision has been made to wind down development of RoboVM.
We have compiled an FAQ to help guide customers through the impact of this announcement. Please contact us at firstname.lastname@example.org for questions not covered by this FAQ.
From April 7, 2016
Starting today, all active Java Champions are eligible to receive IntelliJ IDEA Ultimate for free based upon simple verification. Over the years we have had the opportunity to work with many Java Champions not only a professional level, but we also got to know many of you personally. The feedback that we continue to receive directly contributes to improvements in IntelliJ IDEA and IntelliJ Platform-based products. And for that we thank you and want to show our appreciation.
Default HotSpot Maximum Direct Memory Size
In my previous blog post Improved Documentation of HotSpot Options in Java 8, I wrote about the misunderstandings surrounding the HotSpot JVM's default setting for non-standard option-XX:MaxDirectMemorySize. In this post, I look at a simple way to determine the "default" maximum direct memory size in the HotSpot JVM.