Merry Christmas! After what has been a tough year, my prayer is that this Christmas season will be relaxing and refreshing for us all. To help celebrate the season -- I hope -- I've embedded my church's Christmas program,Christmas Under the Arches. My prayer is that it encourages you all and helps you focus on the Reason we celebrate. :)
JDK 15 hit General Availability today. While I spend most of my time in Kotlin these days, I do keep a close on Java, as it still has a special place in my heart, so I thought I'd make a quick post highlighting some of its new features. :) There are quite a few changes in the release, so I'll list all of them, but focus on the ones I think most developers will find more interesting.
I was recently asked to convert a Spring Boot-based "CLI" to a real CLI utility. It was actually just a normal Spring Boot application with REST endpoints that we'd hit with curl. Pretty ugly. After a few frustrating hours, I finally settled on a solution that seems to work pretty well for us. It uses Spring Boot, of course, as that's our library of choice, plus JCommander for the argument handling. This is a pared-down example of how the application is structured. And because I care about of each you deeply, I'll present it in Java AND Kotlin. :)
For those of you in a hurry, you can get the complete code in my GitHub repo . Everyone else, feel free to read along.
Recently, I started working on a new project and I wanted to give Jooq a go. I also wanted to integrate Flyway : I wanted jOOQ to generate its various classes based off the database schema, and I want to Flyway to create that schema. That's all easy enough, but I'm resisting, right now, committing the generated classes to source control (to avoid the churn and additional maintenance), so how do I make that happen with as little work as possible? How do I make it work in a CI environment? Thanks to Maven, the answer is lots and lots of XML. :) Let's take a look...
Over the years, I've found myself processing a set of data and storing it in a Map, say, something like Map<Long, List<String>> (think something like a list of Room objects, keyed by a building id). I have found myself writing it something like this (in non-idiomatic Kotlin):
val foo = map.get(key)
if (foo == null) {
foo = MutableList<String>()
map.put(key, foo)
}
foo.add(bar)Fortunately, the Kotlin standard library has a better way:
map.getOrPut(key) { mutableListOf() }
.add(bar)If key is not found, the lambda is run, adding the result to Map and return to use the value, new or otherwise, to which we add bar. Much more concise. :) Generally speaking, any time you can let the language/compiler do the work for you, you're going to be better off.
Sample quote
Quote source
My name is Jason Lee. I am a software developer living in the middle of Oklahoma. I’ve been a professional developer since 1997,
using a variety of languages, including Java, Javascript, PHP, Python, Delphi, and even a bit of C#. I currently work for Red Hat
on the WildFly/EAP team, where, among other things, I maintain integrations for some MicroProfile specs, OpenTelemetry, Micrometer,
Jakarta Faces, and Bean Validation. (Full resume here.
LinkedIn profile)
I am the president of the Oklahoma City JUG, and an occasional speaker at the JUG and a variety of technical conferences.
On the personal side, I’m active in my church, and enjoy bass guitar, running, fishing, and a variety of martial arts. I’m also married to a beautiful woman, and have two boys, who, thankfully, look like their mother.
