2aa9e78ddd
* Made minor changes in some patterns such as removed throws clause where not needed, changed incorrect order of arguments in assertEquals * Minor refactorings and code style changes. 1) Removed several use of raw types 2) Removed unnecessary throws clauses 3) Used lambda expressions wherever applicable 4) Used apt assertion methods for readability 5) Use of try with resources wherever applicable 6) Corrected incorrect order of assertXXX arguments * Removed unused import from Promise * Addressed review comments * Addressed checkstyle issue
layout, title, folder, permalink, categories, tags
| layout | title | folder | permalink | categories | tags | ||
|---|---|---|---|---|---|---|---|
| pattern | Converter | converter | /patterns/converter/ | Business Tier |
|
Intent
The purpose of the Converter Pattern is to provide a generic, common way of bidirectional conversion between corresponding types, allowing a clean implementation in which the types do not need to be aware of each other. Moreover, the Converter Pattern introduces bidirectional collection mapping, reducing a boilerplate code to minimum.
Applicability
Use the Converter Pattern in the following situations:
- When you have types that logically correspond which other and you need to convert entities between them
- When you want to provide different ways of types conversions depending on a context
- Whenever you introduce a DTO (Data transfer object), you will probably need to convert it into the domain equivalence