[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 updated TEIIDDES-505:
----------------------------------
Attachment: (was: vdb-model-path-quick-fix-dialog.png)
> 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, vdb-problem-quick-fix-selection.png, vdb-problems-example.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
13 years, 1 month
[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 updated TEIIDDES-505:
----------------------------------
Attachment: vdb-problem-quick-fix-selection.png
> 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, vdb-problem-quick-fix-selection.png, vdb-problems-example.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
13 years, 1 month
[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 updated TEIIDDES-505:
----------------------------------
Attachment: (was: wrong-model-path-in-vdb-warning.png)
> 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, vdb-problem-quick-fix-selection.png, vdb-problems-example.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
13 years, 1 month
[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 updated TEIIDDES-505:
----------------------------------
Attachment: vdb-problems-example.png
> 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, vdb-problem-quick-fix-selection.png, vdb-problems-example.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
13 years, 1 month
[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 edited comment on TEIIDDES-505 at 3/1/13 5:15 PM:
---------------------------------------------------------------
So far I've got VDB validation warnings for the following conditions:
* Model file was deleted from workspace or VDB was imported into the workspace, so no models exist yet
** WARNING: The model file "*ProductsOracle*" in the VDB "*AllProducts.vdb*" does not exist in the workspace
* Model file was renamed in the workspace and a VDB was found containing the model with the same UUID
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" has different name than model *PartsSupplierSQLServer* in workspace
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/sources/PartsSupplierSQLServer.xmi*
** NOTE don't know if we need 2 warnings here, but not warnings are valid
* Model was moved in the workspace but VDB was found containing the model at an old location
** WARNING: The model file "*Employees*" in the VDB "*EmployeeInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/Products.xmi*
was (Author: blafond):
So far I've got VDB validation warnings for the following conditions:
* Model file was deleted from workspace or VDB was imported into the workspace, so no models exist yet
** WARNING: The model file "ProductsOracle" in the VDB "AllProducts.vdb" does not exist in the workspace
* Model file was renamed in the workspace and a VDB was found containing the model with the same UUID
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" has different name than model *PartsSupplierSQLServer* in workspace
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/sources/PartsSupplierSQLServer.xmi*
* Model was moved in the workspace but VDB was found containing the model at an old location
** WARNING: The model file "*Employees*" in the VDB "*EmployeeInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/Products.xmi*
> 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
13 years, 1 month
[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:
---------------------------------------
So far I've got VDB validation warnings for the following conditions:
* Model file was deleted from workspace or VDB was imported into the workspace, so no models exist yet
** WARNING: The model file "ProductsOracle" in the VDB "AllProducts.vdb" does not exist in the workspace
* Model file was renamed in the workspace and a VDB was found containing the model with the same UUID
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" has different name than model *PartsSupplierSQLServer* in workspace
** WARNING: The model file "*PartsSupplier*" in the VDB "*PartsInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/sources/PartsSupplierSQLServer.xmi*
* Model was moved in the workspace but VDB was found containing the model at an old location
** WARNING: The model file "*Employees*" in the VDB "*EmployeeInfo.vdb*" exists in your project but at at different location: */TestRefactorMove/Products.xmi*
> 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
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1610) Unresolved references in transformation column mappings after moving source model in project
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1610?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1610:
-----------------------------------
Attachment: TestRefactorMoveMPS_8.x.zip
> Unresolved references in transformation column mappings after moving source model in project
> --------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1610
> URL: https://issues.jboss.org/browse/TEIIDDES-1610
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.0, 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
> Attachments: TestRefactorMoveMPS_8.x.zip
>
>
> * Import attached model project set
> * Select Products source model in sources folder
> * Right-select the Refactor > Move action
> * Select the root project location for the move and FINISH
> * Multiple validation errors are created like:
> Sql transformation in the model ProductViews contains the unresolved reference file:/home/blafond/Development/Designer/runtime-workspaces/8.1_A/TestRefactorMove/Products.xmi ProductViews.xmi /TestRefactorMove/views Container/SQL Transformation Mapping Root/Mapping
--
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
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1610) Unresolved references in transformation column mappings after moving source model in project
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1610?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1610:
-----------------------------------
Attachment: (was: TestRefactorMoveMPS_8.x.zip)
> Unresolved references in transformation column mappings after moving source model in project
> --------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1610
> URL: https://issues.jboss.org/browse/TEIIDDES-1610
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.0, 8.1
> Reporter: Barry LaFond
> Fix For: 8.1
>
> Attachments: TestRefactorMoveMPS_8.x.zip
>
>
> * Import attached model project set
> * Select Products source model in sources folder
> * Right-select the Refactor > Move action
> * Select the root project location for the move and FINISH
> * Multiple validation errors are created like:
> Sql transformation in the model ProductViews contains the unresolved reference file:/home/blafond/Development/Designer/runtime-workspaces/8.1_A/TestRefactorMove/Products.xmi ProductViews.xmi /TestRefactorMove/views Container/SQL Transformation Mapping Root/Mapping
--
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
13 years, 1 month
[JBoss JIRA] (TEIIDDES-1599) Add VDB resource builder to Designer build process
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1599?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1599.
------------------------------------
Resolution: Done
VdbBuilder was contributed via extension and added to ModelProjectImpl
> Add VDB resource builder to Designer build process
> --------------------------------------------------
>
> Key: TEIIDDES-1599
> URL: https://issues.jboss.org/browse/TEIIDDES-1599
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Validation, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Time Spent: 1 day
> Remaining Estimate: 0 minutes
>
> In order to help users re-synch their VDBs after model refactoring, we need to build (validate) each workspace VDB as an IResource object in order to apply/add problem markers in the workspace.
> May required adding another "Builder" contribution to Designer's .project file.
> The MED builder is the most recent feature that was added which could be a good model for making this happen.
--
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
13 years, 1 month