MapMate - integrations

MapMate is a modern mapping framework in the scope of mapping data in Json, XML, or YAML format into DTOs composed and vice versa.

License	Apache License, Version 2.0
GroupId	com.envimate.mapmate
ArtifactId	integrations-parent
Last Version	1.6.26
Release Date	Dec 3, 2019
Type	pom
Description	MapMate - integrations MapMate is a modern mapping framework in the scope of mapping data in Json, XML, or YAML format into DTOs composed and vice versa.
Project Organization	envimate GmbH

Download integrations-parent

Filename	Size
integrations-parent-1.6.26.pom	1 KB

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/com.envimate.mapmate/integrations-parent/ -->
<dependency>
    <groupId>com.envimate.mapmate</groupId>
    <artifactId>integrations-parent</artifactId>
    <version>1.6.26</version>
    <type>pom</type>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/com.envimate.mapmate/integrations-parent/
implementation 'com.envimate.mapmate:integrations-parent:1.6.26'

Gradle Kotlin

// https://jarcasting.com/artifacts/com.envimate.mapmate/integrations-parent/
implementation ("com.envimate.mapmate:integrations-parent:1.6.26")

Apache Buildr

'com.envimate.mapmate:integrations-parent:pom:1.6.26'

Apache Ivy

<dependency org="com.envimate.mapmate" name="integrations-parent" rev="1.6.26">
  <artifact name="integrations-parent" type="pom" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='com.envimate.mapmate', module='integrations-parent', version='1.6.26')
)

Scala SBT

libraryDependencies += "com.envimate.mapmate" % "integrations-parent" % "1.6.26"

Leiningen

[com.envimate.mapmate/integrations-parent "1.6.26"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

• scanning
• json
• xml
• yaml

MapMate

MapMate solves the problem of (de)serialization and validation of Custom Primitives and general Serializable Objects in a clean and non-invasive way. MapMate enables you to

• Keep validation of your domain in your domain - the factory methods
• Register your validation exceptions and report them aggregated upon deserialization
• Stay independent of the final format of your serialization (YAML/JSON/XML/... - you control)

Rationale

Almost any modern application nowadays is dealing with mapping incoming requests to a subset of Domain Objects and outputting the resulting subset of Domain Objects to a specific format (be that json, yaml, xml, ...).

As a result, we keep writing the "same" code over and over again. We

• parse the Strings into Domain Objects,
• we validate those upon initialization,
• we process the requests and
• we do the mapping again to output a certain Response.

While there are numerous frameworks that help you on some of the stages of this process, we believe there is a need for a simple, non-invasive library that would allow you to integrate this process into your application seamlessly and concentrate on your Business logic.

For an introduction article checkout envimate blog where we build a small example application and explain the usage of Custom Primitives and Data Transfer Objects.

Highlighted features

Some features MapMate offers:

• No Magic - MapMate is using your Objects the same way you would use them, which means:

  • MapMate will not
    • read nor write private fields
    • write values into final fields
    • invoke private methods
  • MapMate will not generate dynamic proxies
  • MapMate does not favour the use of annotations

• Support for validating your domain

  • MapMate allows you to check for validation exceptions and aggregates them accordingly.
  • You will know precisely which field of which domain was faulty.
  • MapMate also offers ways of detecting redundant validation exceptions.

• Non-intrusive usage and configuration

  • MapMate instance can be configured in a single place and offers detection of Custom Primitives and Serialized Objects without the use of annotations.
  • As mentioned above, MapMate creates and validates your Objects the way you would; hence you don't need to change anything in your domain when using MapMate. Since automatic configuration always requires conventions, MapMate allows you to follow your conventions, instead of the ones it's coders came up with.
  • That means your domain stays free of dependencies(direct or conventional) to the (de)serialization and validation frameworks.

• Highly customizable

  • MapMate is highly configurable, allowing configuration for
    • whitelisting and blacklisting packages and/or classes(or even disable the whole classpath scanning and configure objects one-by-one)
    • the detection mechanism of Custom Primitives and Serialized Objects
    • manual definition of Custom Primitives and Serialized Objects
    • customizing the Validation Errors

Resources

Check out these resources, and let us know if you don't find the information you are looking for, we'll be happy to address that.

• QuickStart - Minimal configuration and example usage of MapMate
• User Guide - Detailed description of MapMate functionality, walkthrough features and configuration possibilities
• Introduction Blogpost - Example application, rationale behind MapMate
• Concepts - Terminology we use explained. Check this document out to understand what we call Custom Primitive and Serialized Object and why we choose String as the representation method.

Also, take a look into these articles to get an idea of why we created MapMate in the first place:

• Domain Driven Security

Contributing

General Contribution Guidelines

MapMate is quite young, and the best contribution is using it and giving us feedback.

Open issues, or drop an email to [email protected], let us know how you use it and which features you would like to see.

envimate

Versions

Version
1.6.26 Dec 3, 2019