Java · Spring · Thymeleaf · Htmx
Production-ready Spring Boot, crafted carefully.
I'm Wim Deblauwe, a software developer specialized in Java and Spring. I write books, maintain open-source projects like error-handling-spring-boot-starter, and publish practical, battle-tested articles here.
just start typing — try thymeleaf, testcontainers or htmx
Taming Thymeleaf
Server-side rendering with Spring Boot, step by step.
Modern frontends with htmx
Hypermedia-driven UIs with Spring Boot & Thymeleaf.
Recent posts
showing 4 of 124- Oct 18, 2010 How to expose your flex test code to other Maven modules using flex mojos If you use Maven, you most probably use the excellent flex-mojos plugin to build your flex code. This post will show you how to expose the test code (that does not get included in your normal swc or swf) to other maven modules or projects. This is most useful on bigger projects where you might have some abstract test classes you want to share or builder classes for complex domain objects that you need to create over and over again in unit tests.
- Oct 13, 2010 New (bugfix) release JIRA Database Values Plugin 1.1.1 Quick update: there is a new release of the JIRA Database Values Plugin 1.1.1 because there was an issue with 1.1 if you had issues without a value assigned for your custom field. Download the new version here: https://plugins.atlassian.com/plugin/details/4969
- Oct 9, 2010 New release JIRA Database Values Plugin 1.1 I am proud to announce a new 1.1 version of the JIRA Database Values Plugin. It has the following improvements: Support AJAX lookup in searching: If you use the simple mode for searching in JIRA, you can now select a value from your custom field via AJAX lookup. This makes it a lot easier then that long list of items you might have in the default search mode. The only drawback is that you can only select 1 item. The list allows multi-selection. Use the search.type property in your configuration file to select with search mode you want to use. Support for history and activity view: You can now choose how your value is rendered in the history view and the activity views. In previous versions, the primary key was displayed, which is usually not what you want. Use rendering.changelog.viewpattern in the configuration file to configure this. Note that it is optional as the rendering.viewpattern will be used by default. Support for statistics views: You can now use your custom field in a pie chart, 2d statistics filter and single level group by report. If you want to set a different rendering pattern for these views, use the rendering.statistics.viewpattern key in your properties file. Note that this one does not support HTML, so if your rendering.viewpattern has HTML, you need to add this key and provide a pattern that does not use HTML. Choose how to render NULL values: Previous releases of the plugin always rendered a NULL value as 'Unknown'. As of this release, it will be rendered as an empty string. You can override what is shown by using this: rendering.viewpattern={0} {1,N/A}
- Oct 5, 2010 Using AspectJ and Annotations to document framework pollution in the domain model This blog post will show you how to use Aspectj and Annotations in Java to avoid that certain framework artifacts 'pollute' your code and people start calling methods that you really don’t want when you thought out your design. A concrete example for this if you want to create immutable objects. Value Objects in Domain Driven Design should be like this. You create a constructor for all your object needs, mark all fields final and add some public getters. But now you want to send this object to a Flex client using BlazeDS. You need a default constructor and getters for all properties. Your immutable object, just became highly mutable, just because the framework you use needs this. Same can be said for Hibernate or Coherence that need a default constructor.
no matches for "" — browse the full archive →