search

atlasmap-attic / atlasmap-runtime

AtlasMap runtime engine and design time services
http://atlasmap.io
Other
3 stars 8 forks source link

Support multiple source/target Document #160

Open igarashitm opened 7 years ago

igarashitm commented 7 years ago

Support multiple source/target Document. This is required to have an individual bucket for the Headers/Properties thing apart from payload on both of source and target side. AtlasSession Properties is just a single flat key-value bucket and has no direction (source/target). It doesn't support having a Headers bucket at target side.

Right now, UI partially supports multiple source Document, but runtime doesn't. Multiple target Document is not supported at all.

We might want to have a special docId like CamelMessageHeaders, which automatically populates Camel OUT message headers with its contents.

igarashitm commented 7 years ago

Multiple input is not gonna work neither. Only one SOURCE DataSource is assumed at design level.

igarashitm commented 6 years ago

In order to produce headers/properties thing into individual bucket apart from payload, we need both of multiple input and multiple output support. We might want to have a special docId like CamelMessageHeaders, which automatically populates Camel OUT message headers with its contents.