Maarten Mulders Solution Architect, Speaker & Trainer Whiteboard Addict, Continuous Delivery Junkie & Automated Testing Hippie - If it builds, ship it!

Welcome

This site is intended as a list of personal notes, interesting findings or whatsoever. I hope you’ll find it useful. If so, drop me a line, I would love to hear it!
Feel free to get in touch; for options, see the left pane.

Recent posts

Custom SOAP Faults using Spring WS

There are many situations when you need to write a SOAP-based webservice. Maybe you are writing a test dummy, or maybe you got the interface from some kind of architect. (Yes, there are other reasons, too.) And chances are you’ll be using Spring-WS to do this.

Building ASP.NET Core apps on CircleCI

Recently, my co-worker Willem pulled my attention to the .NET Microservices. Architecture for Containerized .NET Applications e-book. Although I have a strong background in Java and the Java platform, I started reading it, and soon I felt like trying it out. But building software without having automated builds and tests is not the real thing, so that was the first thing I wanted to do. I usually use CircleCI for that, but unfortunately they don’t seem to have an official guide for that.

Simple UML drawing with PlantUML

Every now and then, there’s this moment where you feel a certain urge to draw a diagram. Oftentimes, I feel a similar urge to make a digital version of it. But I don’t always have professional tooling around - and no, PowerPoint or its friends are not what I’m looking for.

Impressions of the first JVMCON

Last Tuesday was the first edition of JVMCON. This conference has a special programme committee: its audience. When the Call for Papers closed, everyone who had a ticket could see the submitted papers. Only, they could not see who submitted the paper - which let them focus on the papers themselves. Out of almost 180 papers, they had to select 13…

I upgraded to Java 9 - Part II

A few weeks ago, I wrote about migrating an existing Spring-application to Java 9. When I finished, two things remained to be investigated:

  1. Code coverage for unit tests.
  2. A bunch of warnings when running the application in Tomcat.