You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All collections must be mapped with the annotation BeanCollection, either on the source or target side. Make sure that the annotation is no longer required. The most important element to scan for is the collection element type on the target side.
Currently, all fields of BeanCollection are individually passed through the internals of BeanMapper. Why not pass those as a collection itself?
The text was updated successfully, but these errors were encountered:
robert-bor
changed the title
Refactor the way BeanCollection settings are passed within BeanMapper
Make sure that internal collections can be mapped without annotation
Nov 1, 2017
Issue #92. BeanMapper is now capable of determining the collection element type of the target collection by examining the generic type. It will use this type as input for the mapping process. BeanCollection.elementType is no longer a required value. BeanMapper will merge collection information from target and source, giving preference to target information.
All collections must be mapped with the annotation BeanCollection, either on the source or target side. Make sure that the annotation is no longer required. The most important element to scan for is the collection element type on the target side.
Currently, all fields of BeanCollection are individually passed through the internals of BeanMapper. Why not pass those as a collection itself?
Works together with issue #90
The text was updated successfully, but these errors were encountered: