Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support complex object mapping #86

Open
syndesis-bot opened this issue Nov 15, 2017 · 4 comments

Comments

@syndesis-bot
Copy link

commented Nov 15, 2017

@igarashitm 2017-09-08 enhancement, UX Design

Right now only the bottommost simple field is targeted for the mapping. It's better to support mapping upper level complex object so that the mapping diagram looks simpler with more complex object.

@syndesis-bot

This comment has been minimized.

Copy link
Author

commented Nov 15, 2017

@mattrpav 2017-09-27

Note: the atlasmap engine does not support complex <-> complex mapping automatically. The specification of a complex class in the definition above is used in order to specify the concrete complex object to be instantiated in order to satisfy the rest of the child mappings.

@syndesis-bot

This comment has been minimized.

Copy link
Author

commented Nov 15, 2017

@mattrpav 2017-09-27

Discussed: Create a UI handler that would support auto-mapping of same or reasonably similar complex objects by automatically creating the list of child mappings as a convenience to the end-user.

Note: I recommend using individual mappings in order to support per-field actions

mmelko pushed a commit to mmelko/atlasmap that referenced this issue Nov 20, 2017

@igarashitm igarashitm added group/uxd and removed notif/uxd labels May 25, 2018

@deernano deernano added the prio/p1 label Aug 7, 2018

@stale

This comment has been minimized.

Copy link

commented Aug 4, 2019

This issue has been automatically marked as stale because it has not had any activity since 90 days. It will be closed if no further activity occurs within 7 days. Thank you for your contributions!

@stale stale bot added the status/stale label Aug 4, 2019

@igarashitm igarashitm removed the status/stale label Aug 4, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.