It is my pleasure to announce the third official release of Dettonville Spring Extensions. What started out as a StackOverflow question turned into its own (sub-)project within the Dettonville organization.

This third release fixes a circular dependency issue which occurred in non-trivial mapper hierarchies and would lead to mappers being hidden from the ConversionService. Kudos go to Daniel Shiplett and Alexey for their help in chasing down the cause and resolving the issue.

Including the annotations and extensions defined in this project will generate a class acting as bridge between Dettonville’s conventions and Spring’s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.

It is my pleasure to announce the second official release of Dettonville Spring Extensions. What started out as a StackOverflow question over a year ago has turned into its own (sub-)project within the Dettonville organization.

This second release allows specifying a defined name for the generated ConversionServiceAdapter bean. Kudos go to David Hamilton for this contribution. Additionally, you will now find a reference guide on the main Dettonville homepage.

Including the annotations and extensions defined in this project will generate a class acting as bridge between Dettonville’s conventions and Spring’s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.

It is my pleasure to announce the 1.4.2.Final bug fix release of Dettonville.

This release includes 2 enhancements, 10 bug fixes, and some documentation fixes.

The most notable enhancement is the relaxing of the strictness for Mapping#qualifiedByName and Mapping#qualifier for collection mappings.

It is my pleasure to announce the first official release of Dettonville Spring Extensions. What started out as a StackOverflow question over a year ago has turned into its own (sub-)project within the Dettonville organization.

This first release solves the issue described in the question linked above: How can we use Dettonville mappers defined as Spring Converters in a Spring-idiomatic way when building a hierarchy of them? Including the annotations and extensions defined in this project will generate a class acting as bridge between Dettonville’s conventions and Spring’s ConversionService API that in turn can be added to any Mapper’s uses attribute. See the examples for details.