If you’re using a StompBrokerRelay on the MessageBrokerRegistry, be careful with your dependencies: If you’re using Spring Boot 1.2.x, you must have <dependency> <groupId>org.projectreactor</groupId> <artifactId>reactor-net</artifactId> </dependency><dependency> <groupId>org.projectreactor</groupId> <artifactId>reactor-net</artifactId> </dependency> on the classpath, in case of Spring Boot 1.3.x, which depends on Spring 4.2 which depends on Reactor 2, it must be <dependency> <groupId>io.projectreactor</groupId> <artifactId>reactor-net</artifactId> </dependency> […]
We’ve been using apiDoc.js in a project for a while. While the resulting documentation looks neat, it has several drawbacks in our Java project. It depends on the full blown NPM stack, doesn’t fit well in a Maven build stack. It can be done via the grunt-maven-plugin and a gruntfile.js, but this is very hard […]
This post has been featured on This Week in Spring – October 13, 2015. Stéphane Nicoll, working at Pivotal, using Spring since early as 2007 and creating Spring Boot with others since 2014 came over from Liege for the third talk at Aachens EuregJUG this year. Stéphane had only two slides with him, the rest […]
This is not about bean testing is effective, right or whatever. Just assume you want your Java beans tested, for example to achieve full code coverage. There are some solutions out there and I used to use the BeanLikeTester but the library and i have different opinions about the hashCode/equals contract so i decided to […]
Most people slice their cakes like this: Image by Elaine Ashton and in most cases not horizontally but still many developers, like i did in the past, slice their packages that way. Really, just slapping classes into packages named “Model”, “View” and “Controller” doesn’t implement that pattern. @jensschauder has written much more eloquent than i […]