[
https://jira.jboss.org/jira/browse/TEIID-377?page=com.atlassian.jira.plug...
]
Steven Hawkins resolved TEIID-377.
----------------------------------
Resolution: Deferred
Deferring post 6.1.1 console work.
Model visibility changes during VDB deployment wizards are not
retained when moving forward and backward through wizard
-----------------------------------------------------------------------------------------------------------------------
Key: TEIID-377
URL:
https://jira.jboss.org/jira/browse/TEIID-377
Project: Teiid
Issue Type: Bug
Components: Console
Affects Versions: 6.0.0
Environment: Console 5.5.3 EA3 - Build 3079
Linux Kernel 2.6.25.14-69
Reporter: Larry O'Leary
Fix For: 6.2.0
Attachments: E2EModelVisibilityTestScript.projectset.zip
When deploying a VDB from within the Console and changing model visibility from the
default settings stored in the VDB, the overridden settings are not kept if one navigates
one step earlier in the VDB deployment wizard. It seems that most users would expect
their setting to be retained if the go forward and backward through a wizard. Kind of
defeats the purpose of Back if it has similar affects to Cancel.
Here is a more detail explanation of what I did. I was performing the E2E Model
Visibility Test Script.
Create a VDB that contains multiple models.
From the MM Console, deploy the VDB using the "New VDB" or "New VDB
Version" button and in Step 3 of the "New Virtual Database Definition
Wizard" or "New Virtual Database Version Definition Wizard" change the
visibility of the models (so as the defaults are not selected).
Click Next
Click Back
Click Back
Click Next
PROBLEM: The default visibility has been reselected and changes to visibility have been
lost
I would expect that the changes made to model visibility would have been retained when
going from Step 4 to Step 3 to Step 2 to Step 3.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira