[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1604?page=com.atlassian.jira.plu... ]
Paul Richardson reassigned TEIIDDES-1604:
-----------------------------------------
Assignee: Paul Richardson
> Switching Default Servers fails because Preview VDBs are not rebuilt.
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1604
> URL: https://issues.jboss.org/browse/TEIIDDES-1604
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> * Created simple Source/View model project
> * Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
> * Started AS7 instance, set as Default Teiid Server
> * Previewed tables from both source and view models
> * Stopped AS7 server
> * Started AS5.1 server
> * Set AS5.1 as Default Teiid Server
> * Tried to preview but got console log parsing errors because it found "import-vdb" element in vdb.xml file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1605) Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ]
Paul Richardson reassigned TEIIDDES-1605:
-----------------------------------------
Assignee: Paul Richardson
> Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1605
> URL: https://issues.jboss.org/browse/TEIIDDES-1605
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
> * Opened Project
> * Tried to Preview a table and got an NPE:
> ** java.lang.NullPointerException
> at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
> at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> The method failing is:
> private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
> String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
> if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
> fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
> }
> return fullVdbName;
>
> }
> ITeiidVdb is a new SPI interface.
> So was the "deployment-name" property available with Teiid 7.7.x runtime?
> Also can't Undeploy VDB on 7.7.2 server
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1605) Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1605:
-----------------------------------
Description:
After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
* Opened Project
* Tried to Preview a table and got an NPE:
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
The method failing is:
private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
}
return fullVdbName;
}
ITeiidVdb is a new SPI interface.
So was the "deployment-name" property available with Teiid 7.7.x runtime?
Also can't Undeploy VDB on 7.7.2 server
was:
After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
* Opened Project
* Tried to Preview a table and got an NPE:
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
The method failing is:
private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
}
return fullVdbName;
}
ITeiidVdb is a new SPI interface.
So was the "deployment-name" property available with Teiid 7.7.x runtime?
> Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1605
> URL: https://issues.jboss.org/browse/TEIIDDES-1605
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
>
> After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
> * Opened Project
> * Tried to Preview a table and got an NPE:
> ** java.lang.NullPointerException
> at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
> at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> The method failing is:
> private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
> String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
> if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
> fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
> }
> return fullVdbName;
>
> }
> ITeiidVdb is a new SPI interface.
> So was the "deployment-name" property available with Teiid 7.7.x runtime?
> Also can't Undeploy VDB on 7.7.2 server
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1605) Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1605?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1605:
-----------------------------------
Description:
After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
* Opened Project
* Tried to Preview a table and got an NPE:
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
The method failing is:
private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
}
return fullVdbName;
}
ITeiidVdb is a new SPI interface.
So was the "deployment-name" property available with Teiid 7.7.x runtime?
was:
After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
* Opened Project
* Tried to Preview a table and got an NPE:
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
> -------------------------------------------------------------------------------
>
> Key: TEIIDDES-1605
> URL: https://issues.jboss.org/browse/TEIIDDES-1605
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
>
> After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
> * Opened Project
> * Tried to Preview a table and got an NPE:
> ** java.lang.NullPointerException
> at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
> at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> The method failing is:
> private String getFullDeployedVdbName(ITeiidVdb deployedVdb) {
> String fullVdbName = deployedVdb.getPropertyValue("deployment-name");;
> if (!fullVdbName.endsWith(Vdb.FILE_EXTENSION)) {
> fullVdbName = fullVdbName + Vdb.FILE_EXTENSION;
> }
> return fullVdbName;
>
> }
> ITeiidVdb is a new SPI interface.
> So was the "deployment-name" property available with Teiid 7.7.x runtime?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1605) Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1605:
--------------------------------------
Summary: Issues preview data after switch from 7.7.x Teiid to 8.2.x Teiid default server
Key: TEIIDDES-1605
URL: https://issues.jboss.org/browse/TEIIDDES-1605
Project: Teiid Designer
Issue Type: Feature Request
Components: Data Preview, VDB & Execution
Affects Versions: 8.1
Reporter: Barry LaFond
Fix For: 8.1
After switch from 8.2.x Teiid server to 7.7.x Teiid server, closing the project and deleting the Preview VDBs from the local files system (local eclipse workspace).....
* Opened Project
* Tried to Preview a table and got an NPE:
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1604?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1604:
-----------------------------------
Description:
* Created simple Source/View model project
* Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
* Started AS7 instance, set as Default Teiid Server
* Previewed tables from both source and view models
* Stopped AS7 server
* Started AS5.1 server
* Set AS5.1 as Default Teiid Server
* Tried to preview but got console log parsing errors because it found "import-vdb" element in vdb.xml file
was:
* Created simple Source/View model project
* Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
* Started AS7 instance, set as Default Teiid Server
* Previewed tables from both source and view models
* Stopped AS7 server
* Started AS5.1 server
* Set AS5.1 as Default Teiid Server
* Tried to preview NPE in Designer
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Switching Default Servers fails because Preview VDBs are not rebuilt.
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1604
> URL: https://issues.jboss.org/browse/TEIIDDES-1604
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
>
> * Created simple Source/View model project
> * Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
> * Started AS7 instance, set as Default Teiid Server
> * Previewed tables from both source and view models
> * Stopped AS7 server
> * Started AS5.1 server
> * Set AS5.1 as Default Teiid Server
> * Tried to preview but got console log parsing errors because it found "import-vdb" element in vdb.xml file
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1604?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1604:
-----------------------------------
Description:
* Created simple Source/View model project
* Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
* Started AS7 instance, set as Default Teiid Server
* Previewed tables from both source and view models
* Stopped AS7 server
* Started AS5.1 server
* Set AS5.1 as Default Teiid Server
* Tried to preview NPE in Designer
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
was:
* Created simple Source/View model project
* Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
* Started AS7 instance, set as Default Teiid Server
* Previewed tables from both source and view models
* Stopped AS7 server
* Started AS5.1 server
* Set AS5.1 as Default Teiid Server
* Tried to preview but View model did not Deploy
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
> Switching Default Servers fails because Preview VDBs are not rebuilt.
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1604
> URL: https://issues.jboss.org/browse/TEIIDDES-1604
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Data Preview, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
>
> * Created simple Source/View model project
> * Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
> * Started AS7 instance, set as Default Teiid Server
> * Previewed tables from both source and view models
> * Stopped AS7 server
> * Started AS5.1 server
> * Set AS5.1 as Default Teiid Server
> * Tried to preview NPE in Designer
> ** java.lang.NullPointerException
> at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
> at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
> at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-1604) Switching Default Servers fails because Preview VDBs are not rebuilt.
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1604:
--------------------------------------
Summary: Switching Default Servers fails because Preview VDBs are not rebuilt.
Key: TEIIDDES-1604
URL: https://issues.jboss.org/browse/TEIIDDES-1604
Project: Teiid Designer
Issue Type: Feature Request
Components: Data Preview, VDB & Execution
Affects Versions: 8.1
Reporter: Barry LaFond
Fix For: 8.1
* Created simple Source/View model project
* Created Both AS5.1 + Teiid 7.x and AS7.1.1 + Teiid 8.2 server instances
* Started AS7 instance, set as Default Teiid Server
* Previewed tables from both source and view models
* Stopped AS7 server
* Started AS5.1 server
* Set AS5.1 as Default Teiid Server
* Tried to preview but View model did not Deploy
** java.lang.NullPointerException
at org.teiid.designer.runtime.preview.PreviewManager.getFullDeployedVdbName(PreviewManager.java:642)
at org.teiid.designer.runtime.preview.PreviewManager.previewSetup(PreviewManager.java:1373)
at org.teiid.designer.runtime.ui.preview.PreviewDataWorker$1.run(PreviewDataWorker.java:233)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-505?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-505:
---------------------------------------
For clarity, the VDBs in these scenarios are error-free, by themselves. They could have warnings, but are fully deployable and made ACTIVE in a Teiid server.
The warnings are because the VDBs are being made "out of sync" with the workspace by performing workspace model refactoring, which doesn't automatically update the VDBs if they contain *Copies* of the models in the workspace.
> Refactored file is not reflected in VDB (no corresponding file in workspace)
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-505
> URL: https://issues.jboss.org/browse/TEIIDDES-505
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, VDB & Execution
> Affects Versions: 7.0
> Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.1
>
> Attachments: model-vdb-dependency-warning-dialog.png, vdb-model-path-quick-fix-dialog.png, wrong-model-path-in-vdb-warning.png
>
>
> I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace".
> I believe the VDB's contents should have been involved in the refactoring, just like other files.
> There are numerous scenarios of VDBs that are out of synch with their workspace if they create multi-model VDBs in a project and begin moving, renaming or deleting files from that same project. Below are a few scenarios that cover the simplest and most common use cases.
> *Scenario 1*: *Refactor > Move* source model.
> * User has source model in a VDB and the model exists in the workspace
> * User *moves* the source model to different folder in project
> * *Result*: VDB now has source model path that is not valid
> * *Desired End State*: VDB's source model path is updated to reflect new project location
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Move* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the path is out of sync with model in workspace
> ** Provide Quick Fix action to fix the model path in the VDB
> *Scenario 2*: *Refactor > Move* source model.
> * User has source and dependent view model in a VDB and the models exist in the workspace
> * User moves a source model to different folder in project
> * *Result*: VDB now has source model path that is not valid
> * *Result*: VDB now contains view model that is out of sync with workspace model due to updated model import statement
> * *Desired End State*: VDB's source model path is updated to reflect new project location and view model is synchronized
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Move* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** The VdbBuilder creates validation Warning marker stating the path is out of sync with model in workspace
> ** The VdbBuilder creates validation Warning marker stating the view model is out of sync
> ** Provide Quick Fix action to fix the source model path and update the view model in the VDB
> *Scenario 3*: *Delete* source model
> * User has source model in a VDB and the model exists in the workspace
> * User *deleted* the source model
> * *Result*: VDB now has source model that does NOT exist in workspace
> * *Desired End State*: Source model is replaced in proper location in workspace
> * *Proposed Solution*:
> ** Display a dialog when launching Delete action warning user that VDBs exist in project that containing the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the source model does NOT exist in the workspace
> *Scenario 4*: *Refactor > Rename* source model
> * User has source model in a VDB and the model exists in the workspace
> * User *renames* the source model
> * *Result*: VDB now has source model with wrong name
> * *Desired End State*: VDB's source model is replaced in the VDB
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Rename* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the source model does NOT exist in the workspace
> ** Add a VDB Refactor Model handler that can work with refactoring framework to swap out the source model in the VDB
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months
[JBoss JIRA] (TEIIDDES-505) Refactored file is not reflected in VDB (no corresponding file in workspace)
by Van Halbert (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-505?page=com.atlassian.jira.plug... ]
Van Halbert commented on TEIIDDES-505:
--------------------------------------
I disagree with calling it a warning. Its really an error, and with this issue, Teiid will not make the VDB active. If Teiid would activate the VDB, then a warning would be appropriate, because it the vdb could still be used.
> Refactored file is not reflected in VDB (no corresponding file in workspace)
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-505
> URL: https://issues.jboss.org/browse/TEIIDDES-505
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, VDB & Execution
> Affects Versions: 7.0
> Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7 Final
> Reporter: Paul Nittel
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 8.1
>
> Attachments: model-vdb-dependency-warning-dialog.png, vdb-model-path-quick-fix-dialog.png, wrong-model-path-in-vdb-warning.png
>
>
> I created a VDB which contained source and view models. I Refactor > Renamed one virtual model. When I opened the VDB, the original file was present and, when the mouse hovered over the file, this message was displayed, "This entry has no corresponding file in the workspace".
> I believe the VDB's contents should have been involved in the refactoring, just like other files.
> There are numerous scenarios of VDBs that are out of synch with their workspace if they create multi-model VDBs in a project and begin moving, renaming or deleting files from that same project. Below are a few scenarios that cover the simplest and most common use cases.
> *Scenario 1*: *Refactor > Move* source model.
> * User has source model in a VDB and the model exists in the workspace
> * User *moves* the source model to different folder in project
> * *Result*: VDB now has source model path that is not valid
> * *Desired End State*: VDB's source model path is updated to reflect new project location
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Move* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the path is out of sync with model in workspace
> ** Provide Quick Fix action to fix the model path in the VDB
> *Scenario 2*: *Refactor > Move* source model.
> * User has source and dependent view model in a VDB and the models exist in the workspace
> * User moves a source model to different folder in project
> * *Result*: VDB now has source model path that is not valid
> * *Result*: VDB now contains view model that is out of sync with workspace model due to updated model import statement
> * *Desired End State*: VDB's source model path is updated to reflect new project location and view model is synchronized
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Move* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** The VdbBuilder creates validation Warning marker stating the path is out of sync with model in workspace
> ** The VdbBuilder creates validation Warning marker stating the view model is out of sync
> ** Provide Quick Fix action to fix the source model path and update the view model in the VDB
> *Scenario 3*: *Delete* source model
> * User has source model in a VDB and the model exists in the workspace
> * User *deleted* the source model
> * *Result*: VDB now has source model that does NOT exist in workspace
> * *Desired End State*: Source model is replaced in proper location in workspace
> * *Proposed Solution*:
> ** Display a dialog when launching Delete action warning user that VDBs exist in project that containing the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the source model does NOT exist in the workspace
> *Scenario 4*: *Refactor > Rename* source model
> * User has source model in a VDB and the model exists in the workspace
> * User *renames* the source model
> * *Result*: VDB now has source model with wrong name
> * *Desired End State*: VDB's source model is replaced in the VDB
> * *Proposed Solution*:
> ** Display a dialog when launching *Refactor > Rename* action warning user that VDBs exist in project that contain the selected model and possible side-effects
> ** Add a VdbBuilder that creates validation Warning marker stating the source model does NOT exist in the workspace
> ** Add a VDB Refactor Model handler that can work with refactoring framework to swap out the source model in the VDB
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 2 months