[JBoss JIRA] Moved: (TEIIDDES-1058) Importing a .vdb into a different named project than what it was created will cause java.lang.IllegalArgumentException when a model in the vdbeditor is doubleclicked
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1058?page=com.atlassian.jira.plu... ]
Van Halbert moved SOA-3346 to TEIIDDES-1058:
--------------------------------------------
Project: Teiid Designer (was: JBoss Enterprise SOA Platform)
Key: TEIIDDES-1058 (was: SOA-3346)
Affects Version/s: 7.4.2
(was: JBDS)
Component/s: Editors
(was: Tooling)
(was: EDS)
Security: (was: Public)
> Importing a .vdb into a different named project than what it was created will cause java.lang.IllegalArgumentException when a model in the vdbeditor is doubleclicked
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1058
> URL: https://issues.jboss.org/browse/TEIIDDES-1058
> Project: Teiid Designer
> Issue Type: Bug
> Components: Editors
> Affects Versions: 7.4.2
> Reporter: Van Halbert
> Assignee: Van Halbert
>
> Imported a the models and .vdb file for a project (i.e., Loopback) into designer under a different project name (i.e, Loopback2). When I opened the vdb editor and tried to doubleclick the souce model (just pick any model), it produced the attached doubleclick.txt error in the log file.
> The cause is because the "Path" in the vdb points to a non-existent project.
> Talking with Barry, what should probably happen is upon the designer opening the vdb in the editor, it should verify the paths are valid and provide an indicator when a model can't be found. And when a model is flagged as not being found, the vdbeditor shouldn't process the double click.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months