[
https://issues.jboss.org/browse/TEIIDDES-741?page=com.atlassian.jira.plug...
]
John Doyle resolved TEIIDDES-741.
---------------------------------
Fix Version/s: 7.2
Resolution: Done
I extended the DTP wizard and page classes to enable us to pass the connection profile
info through to the page, and set the driver drop down to the correct driver.
I also change the behavior of the action such that it uses the profile if it exists,
creates the profile and moves to the DTP perspective if all of the required info is
present and the profile does not exist, or brings up the "New Connection
Profile" dialog is some information is lacking and the profile does not exist.
This also required a further qualification of the profile name. Profiles we create with
the "Execute" action are now named as VDBName - HostName - Teiid Connection
Execute VDB Action does not always set the correct VDB name in the
VDB name property.
-------------------------------------------------------------------------------------
Key: TEIIDDES-741
URL:
https://issues.jboss.org/browse/TEIIDDES-741
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 7.1.1
Environment: JBDS Beta 2
Reporter: John Doyle
Assignee: John Doyle
Priority: Blocker
Fix For: 7.1.1, 7.2
I haven't figured out why, but sometimes the Execute VDB action comes up with the
right VDB name, and sometimes it comes up with the wrong name, and existing VDB, but not
the one you're trying to execute.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira