Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#221 map-id on mapping makes it non-default

Dozer v5.2
closed-invalid
dmitry (lv)
5
2010-05-16
2009-09-14
Stephen Todd
No

I have the below mapping:

<mappings>

<mapping map-id="RemoteFoo">
<class-a>com.example.Foo</class-a>
<class-b>com.example.RemoteFoo</class-b>
<field>
<a>bar</a>
<b>barPrime</b>
</field>
</mapping>

<mapping map-id="RemoteSearchResults-RemoteFoo">
<class-a>com.example.SearchResults</class-a>
<class-b>com.example.RemoteSearchResults</class-b>
<field map-id="RemoteFoo">
<a>results</a>
<b>results</b>
<a-hint>com.example.Foo</a-hint>
<b-hint>com.example.RemoteFoo</b-hint>
</field>
</mapping>

</mappings>

When I use a mapper with the above configuration to map Foo<-->RemoteFoo without specifying the map-id, the mapping above ("RemoteFoo") isn't used. Instead the object is mapped as if "RemoteFoo" didn't exist.

Discussion

  • Stephen Todd
    Stephen Todd
    2009-09-14

    • summary: map-id on mapping make it non-default --> map-id on mapping makes it non-default
     
  • dmitry (lv)
    dmitry (lv)
    2010-05-16

    • assigned_to: nobody --> buzdin
    • status: open --> closed-invalid