#62 improve collection handling, esp. non-cumulative mapping

closed
None
5
2007-04-27
2006-05-05
Matt Benson
No

Currently non-cumulative mapping replaces the existing
object with a new one, mapping the existing one to the
new one. This drives e.g. Hibernate crazy,
necessitating a merge() operation, and will most often
blow away changes the destination object was intended
to receive as part of the mapping operation in the
first place. The attached patch will correct this
error for set, list, and array handling. Additionally
it removes the superfluous mapSetToSet() method (the
logic for mapping any collection to a Set is superior,
including non-cumulative support) and adds
non-cumulative support when mapping maps to maps (using
key AND value equality). Patch created against Dozer
21XBranch.

Discussion

  • Matt Benson

    Matt Benson - 2006-05-19
    • assigned_to: nobody --> orangeherbert
     
  • Matt Benson

    Matt Benson - 2006-06-02

    updated patch; fixes issue whereby super fieldmappings weren't picked up.

     
  • Matt Tierney

    Matt Tierney - 2006-11-13
    • assigned_to: orangeherbert --> mhtierney
     
  • Matt Tierney

    Matt Tierney - 2007-04-24

    Logged In: YES
    user_id=1236069
    Originator: NO

    Applied non-cum portion of the patch

     
  • Matt Tierney

    Matt Tierney - 2007-04-24
    • status: open --> pending
     
  • Matt Tierney

    Matt Tierney - 2007-04-27
    • status: pending --> closed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks