- This page configures the target type.
- Two options on this page (mutually exclusive):
- If the type is XML, XSD, JSON, or JSON Schema, provide browser for file as we do today
- If the type is “Other”, the user needs to provide two pieces of data:
- select from a drop-down of existing data format definitions (this can be queried from the config builder)
- specify the target class used for the mapping
- Finish is enabled once the target configuration is specified.
Another idea I’ve been playing around with is removing support for changing the source and target types in the editor and instead allowing the user to select the target type in the wizard. Since changing a source or target type invalidates all mappings anyway, I don’t think this is much of an inconvenience. It also makes life simpler as we won’t need to change the Camel config from within the mapper editor any longer to update source/target types. If we went ahead with this plan, then my comments above about skipping the source/target pages in the wizard would no longer apply. Instead, we would have a page where the user had a type browser where they selected the source and target type on each page.
Hopefully, this all makes sense. If no, let me know. :-)
regards,
keith