In one of my projects I let Spring Boot automatically bind domain objects from the database.
This fails in the reduced unit test setup, because DomainClassConverter
is not available. But it can be mocked!
In one of my projects I let Spring Boot automatically bind domain objects from the database.
This fails in the reduced unit test setup, because DomainClassConverter
is not available. But it can be mocked!
When I started to use Spring Boot I had some issues with the validation. The @Validated annotation triggered the validation as requested but the validation terminated with an org.springframework.validation.BindException
instead of filling the BindingResult
object.
On our default setup, we use Apache as proxy and load balancer for our applications. This usually works, but caused problems with Thumbor.
During learning Spring Boot I noticed attributes to methods in Spring Boot controllers can be automatically injected.
To migrate my blog from Grails to Spring Boot I created an implementation to inject the current blog instance based on an session attribute.
Using the asset pipline in Grails, the production CSS and Javascript files have been including with a digest appendix. This feature is not available in Spring Boot, therefore I started to create a simple Thymeleaf tag library.
I recently bought the 2.9″ ESPaper Plus Kit, WiFi ePaper display from ThingPulse.
To get this device working with my ansible configured SSL webproxy I had to get some additional debugging skills...
My Seafile instance is running on a dedicated webserver behind a reverse proxy which is handling the SSL encryption.
This setup with the protocol change on one of the webservers does not work out of the box / this case is not documented in the official server documentation.
Um im Sommer Pflanzen nicht zu vernachlässigen habe ich das das Projekt einer automatischen Bewässerungsanlage gestartet... als Testumgebung nutze ich den Topf mit den Kräutern.
I use the squeeze-backport of redmine on Debian.
With the default setup, all the Ajax-Post-Requests cause the logout of the current user due to the missing X-CSRF-Token.
Because I could not find a complete solution, I backported the CSRF-Code from a newer relase.
Der zweite Blog mit der neuen Grails Blog Software ist online.
© 2015 - 2022 Moritz Kobel
Theme by Anders Noren — Up ↑