Uploaded image for project: 'Teiid Designer'
  1. Teiid Designer
  2. 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


    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 7.4.2
    • Fix Version/s: 7.5, 7.4.2
    • Component/s: Editors
    • Labels:
    • Release Notes Text:
      Double-clicking in a VDB Editor on a model that does not have a corresponding copy in the workspace no longer throws an exception.


      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.

        Gliffy Diagrams


            Issue Links



                • Assignee:
                  elvisisking Daniel Florian
                  van.halbert Van Halbert
                • Votes:
                  0 Vote for this issue
                  1 Start watching this issue


                  • Created: