Bug 780887 (SOA-3345) - 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
Summary: Importing a .vdb into a different named project than what it was created will...
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-3345
Product: JBoss Enterprise SOA Platform 5
Classification: JBoss
Component: Tooling, EDS
Version: JBDS
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 5.2.0.ER4
Assignee: Van Halbert
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-01 18:13 UTC by Van Halbert
Modified: 2011-10-10 20:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-10-10 20:49:23 UTC
Type: Bug

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-3345 0 None None None Never
Red Hat Issue Tracker TEIIDDES-1058 0 None None None Never

Description Van Halbert 2011-09-01 18:13:18 UTC 
project_key: SOA

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.
Comment 1 Van Halbert 2011-09-01 18:13:49 UTC 
Link: Added: This issue Cloned to SOA-3346
Comment 2 Anne-Louise Tangring 2011-09-06 13:57:20 UTC 
Van to investigate to see if we can get it fixed this week.
Comment 4 Paul Nittel 2011-10-10 20:49:23 UTC 
Tested and closed!
Note You need to log in before you can comment on or make changes to this bug.