[
https://issues.jboss.org/browse/TEIIDDES-2671?page=com.atlassian.jira.plu...
]
Barry LaFond commented on TEIIDDES-2671:
----------------------------------------
The Dynamic VDB editor has no real functionality. I think the solution is to remove the
UI contribution and users will use their own/other XML editors if they wish.
Note that the VDB export is designed to be a snapshot representation of a Archive VDB.. so
users will have to determine if/what they want to change in the dyn. vdb once generated.
Dynamic VDB Editor is set as default for all XML files
------------------------------------------------------
Key: TEIIDDES-2671
URL:
https://issues.jboss.org/browse/TEIIDDES-2671
Project: Teiid Designer
Issue Type: Bug
Components: Editors
Affects Versions: 9.0.4
Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.4.CR1 (Teiid Designer
9.0.4.CR1-v20150917-2111-B1187 )
Reporter: Andrej Podhradsky
Priority: Blocker
Fix For: 9.0.4, 9.2
Dynamic VDB Editor is set as default for all XML files. As a consequence opening an XML
file fails due to
org.eclipse.ui.PartInitException: File blueprint.xml is not a dynamic VDB
In the example above the blueprint.xml should be opened by Camel Editor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)