[JBoss JIRA] Created: (JBIDE-7574) Delete sub mappings on CollectionMapping addition
by Tom Fennelly (JIRA)
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
15 years, 4 months
[JBoss JIRA] Created: (JBIDE-7698) JBT 3.2.0 Beta2 contains invalid org.jdom plugin
by Snjezana Peco (JIRA)
JBT 3.2.0 Beta2 contains invalid org.jdom plugin
------------------------------------------------
Key: JBIDE-7698
URL: https://jira.jboss.org/browse/JBIDE-7698
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.2.0.Beta2
Reporter: Snjezana Peco
Assignee: Nick Boldt
JBT 3.2.0 Beta2 (v20101121-0147-H262-Beta2, for instance) contains the org.jdom plugin that is invalid.
The plugin is unpacked and contains invalid signed information in the MANIFEST.MF file. Eclipse won't load any classes from the plugin.
The problem can't always be reproduced because WTP also contains this plugin (valid) and in the case P2 chooses the plugin from WTP, the problem won't happen.
Steps to reproduce:
- install WTP to the dropins/wtp folder and JBT to the dropins/jbt folder
- start Eclipse with the -clean option (P2 will select org.jdom from the JBT distribution)
You can also change bundles.info.
- checkout the o.j.t.ws.ui plugin
the o.j.t.ws.ui plugin will contain compile errors (DOMBuilder cannot be resolved to a type).
JBDS 4.0.0 Beta2 includes a valid the org.jdom plugin.
Solution: removing the org.jdom from JBT or creating a valid the org.jdom plugin.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
15 years, 4 months