[
https://jira.jboss.org/browse/JBIDE-7574?page=com.atlassian.jira.plugin.s...
]
Brian Fitzpatrick resolved JBIDE-7574.
--------------------------------------
Resolution: Done
Jiri, Tom will update this with details later today - but I'm resolving it for now so
it doesn't appear on Max's radar. If we have further work to do, we can set it for
CR1
Delete sub mappings on CollectionMapping addition
-------------------------------------------------
Key: JBIDE-7574
URL:
https://jira.jboss.org/browse/JBIDE-7574
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: smooks
Reporter: Tom Fennelly
Assignee: Tom Fennelly
Fix For: 3.2.0.Beta2
For sources that don't have a schema (e.g. sample xml source), the editor has to
allow the user perform mappings that it can normally block the user from doing in
situations where there is a schema (e.g. XSD source) e.g. based on schema rules, it can
block mapping to sub elements before a parent collection mapping is made etc.
For these sources that don't have a schema, the user could map into a sub element on
the target and then (later), perform a collection based mapping onto one of the parent
elements. This CollectionMapping can invalidate the earlier mappings. In such cases, the
earlier mappings need to be deleted and the user needs to remap.
We could get "fancy" in future and actually fix the earlier mappings to make
them part of the new Collection, but deleting the earlier mappings is easier for now.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira