Version 2.1 of DD4T has seen many improvements and changes with respect to the DD4T 2.0.X branch. While most changes are compatible with 2.0.X, it is recommended to upgrade your web application to the 2.1.X version. The main reason is that the 2.0.X releases will be discontinued and active development on it has stopped. Additionally, new versions of the DD4T Template Building Blocks may push new data formats or properties to the front end and these will only be incorporated in the DD4T 2.1 branch. New implementations are further encouraged to use the latest version, even if you already have published DD4T 1.0 XML or DD4T 2.0.X / 2.1.X Json in your Broker database, in order make use of the latest support for libraries, Tridion and fixed issues.
All posts by Raimond Kempees
Introducing DD4T Version 2.1 for Java
As is tradition by now to release new full versions in the last days of the year, the end of 2017 brings again a brand new release of DD4T and it sure is by now a battle hardened, try to kill me but you won’t be able to release in full use at quite a few high volume and high load production environments.
Going polymorph with ViewModels in DD4T Java 2.0
Plato (~423 BC – ~347 BC) was a pretty smart guy. Among his many ideas and thoughts, his Theory of Forms had an immense influence on how we perceive and solve the philosophical Problem of universals. It basically comes down to the idea that every physical object has one or more essences (or Forms) and that if that object would not have that Form, it would not be that object: a dog is Mammal, but a giraffe is also a Mammal. What makes both animals Mammals? It’s, simply put, the Idea of the Mammal.
ViewModel functionality in DD4T 2.0 for Java Part III – Complex Field Types
In part II of these series on ViewModel functionality in dd4t–2-java, it was explained how to create ViewModel classes and how to implement basic field types for the mapping between Tridion fields and DD4T ViewModel properties.
This post handles the more complex field types. The reason we make a distinction between ‘simple’ and ‘complex’ is mainly because the complex field types have more options to be deserialized into and need quite some help from DD4T to know what they will become.
ViewModel functionality in DD4T 2.0 for Java Part II – Creating ViewModels
In the previous article in this series, we had an in-depth look into how the ViewModels mechanism works in DD4T 2 for Java. This part covers the practical aspects and the basics on how to create your own ViewModels as well as having a look at how Tridion field types map to Java Object types.
Continue reading