[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-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, 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, 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 updated TEIIDDES-505:
----------------------------------
Attachment: 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, 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, 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 updated TEIIDDES-505:
----------------------------------
Attachment: model-vdb-dependency-warning-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
>
>
> 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, 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 would say dropping in a VDB would be another scenario, besides deleting source model. Which has its own result and desired effect.
> 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
>
>
> 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, 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 updated TEIIDDES-505:
----------------------------------
Description:
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
was:
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
** Provide Quick Fix action to extract the source model from the VDB and place it in the proper location 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
> 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
>
>
> 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, 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:
---------------------------------------
The scenario might really be that a user imports/drops a VDB into their workspace.
* What error/warning/messages should be attached to that VDB
* What, if anything, should Designer do to help the user make it "editable" or synched with workspace
Issues include:
* Project where the VDB is dropped will probably be different than the project defined in the model paths in VDB
* We do not support renaming Model Projects
* Synching might mean "extract all models" into workspace
** Change Project name in Model paths to working Project
** Keep all project folders as defined in VDB
** Extract copies of VDB models into workspace and validate
> 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
>
>
> 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
> ** Provide Quick Fix action to extract the source model from the VDB and place it in the proper location 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, 2 months
[JBoss JIRA] (TEIIDDES-1489) Document setup preferences for using the Server View for Teiid
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1489?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1489.
---------------------------------------
Resolution: Done
> Document setup preferences for using the Server View for Teiid
> --------------------------------------------------------------
>
> Key: TEIIDDES-1489
> URL: https://issues.jboss.org/browse/TEIIDDES-1489
> Project: Teiid Designer
> Issue Type: Task
> Components: Documentation
> Affects Versions: 8.0
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> Need to make clear to the user, how to setup the Server View in JBoss Tools for use with Teiid. Specifically, the user will need to edit the JBoss Runtime preferences to point to "standalone-teiid.xml" config file which we provide with the Teiid install.
> * Need a chapter before the 'Dive Right in' example detailing the configuring of the teiid server.
> * Update the UI Reference section on the Teiid View with new UI changes
--
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, 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:
--------------------------------------
Scenario 3 - Delete Source Model
Wouldn't the desired state be the VDB has the source model removed (as well as any dependent view models)? Don't understand what "Source model is replaced in proper location in workspace" when its being deleted.
And this would also include the quick fix.
> 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
>
>
> 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
> ** Provide Quick Fix action to extract the source model from the VDB and place it in the proper location 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, 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 updated TEIIDDES-505:
----------------------------------
Description:
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
** Provide Quick Fix action to extract the source model from the VDB and place it in the proper location 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
was:
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.
> 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
>
>
> 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
> ** Provide Quick Fix action to extract the source model from the VDB and place it in the proper location 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, 2 months
[JBoss JIRA] (TEIIDDES-1569) REST Extension Properties not Visible for Procedure
by luca gioppo (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1569?page=com.atlassian.jira.plu... ]
luca gioppo commented on TEIIDDES-1569:
---------------------------------------
I used the published 8.0 zip to create the procedures and did not manage to get the enable rest
With the #2179 build (8.1beta1 it seems)there is the wizard, but it did not gave me the option to add the rest to procedures created with the 8.0
Let me know if I have to make some test more.
With the #2179 all seems to work correctly and lso the xmlliteral did not represent anymore (just the first time) it create an object but I can change the data type and have no error or have to restart eclipse.
Luca
> REST Extension Properties not Visible for Procedure
> ---------------------------------------------------
>
> Key: TEIIDDES-1569
> URL: https://issues.jboss.org/browse/TEIIDDES-1569
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Web Services Support
> Affects Versions: 8.0
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: org.teiid.designer.dqp.patch
>
>
> REST properties (URI, PATH and METHOD) are not displaying in the properties panel for a virtual procedure.
--
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, 2 months