[JBoss JIRA] (TEIIDDES-1611) Add action to copy models from a VDB into your workspace project
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1611?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1611:
----------------------------------------
* VdbBuilder creates warning markers for any model in a VDB that doesn't exist in workspace
* Added Quick Fix to Extract any missing model from a VDB and place it a corresponding project and/or folder
** This will result in different validation warnings that the model paths in the VDB are different than the workspace
** User can then use other Quick Fix to sync the VDB
* Added Quick Fix to perform both the VDB Model extract as well as synchronizing VDB resulting in no warnings and the VDB is now up-to-date
> Add action to copy models from a VDB into your workspace project
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1611
> URL: https://issues.jboss.org/browse/TEIIDDES-1611
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> TEIIDDES-505 covered most of the refactoring issues with models in a workspace/project. However, the remaining use-case of importing a VDB into a project and trying to work with it has not been covered yet.
> This feature would provide a means to extract/copy contents of a VDB and construct a corresponding file structure of folders/models within the VDB. This would be a "reverse-synch" methodology and allow users to use VDBs as a starting point for their modeling as well as the "ending point".
--
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-1612) Extra Transformation nested mappings created for simple SELECT transformation
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1612:
--------------------------------------
Summary: Extra Transformation nested mappings created for simple SELECT transformation
Key: TEIIDDES-1612
URL: https://issues.jboss.org/browse/TEIIDDES-1612
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 8.1
Reporter: Barry LaFond
Assignee: Paul Richardson
Fix For: 8.1
Created a simple PARTS transformation and ended up with extra column mappings in transformation mapping root. Below is XMI segments from a correct 7.8 generated model and the latest 8.1 Designer version.
*DESIGNER 7.8 PARTS TRANSFORMATION*
{code:xml}
<transformation:TransformationContainer xmi:uuid="mmuuid:faa98ced-0d3a-40a7-afde-37352988a466">
<transformationMappings xsi:type="transformation:SqlTransformationMappingRoot" xmi:uuid="mmuuid:d9def113-e28c-4e17-b1fd-b2ea73d853c6" outputs="mmuuid/e463aa86-95c6-4c51-917a-f8d992e9eb07" target="mmuuid/e463aa86-95c6-4c51-917a-f8d992e9eb07">
<helper xsi:type="transformation:SqlTransformation" xmi:uuid="mmuuid:426c1504-5843-46c4-a65b-638a81b8d920">
<nested xsi:type="transformation:SqlTransformation" xmi:uuid="mmuuid:fef73d6a-ab79-440c-9ab6-3815eaf67737" selectSql="SELECT PartsSupplierA.PARTS.PART_ID AS ID, PartsSupplierA.PARTS.PART_NAME AS NAME, PartsSupplierA.PARTS.PART_COLOR AS COLOR, PartsSupplierA.PARTS.PART_WEIGHT AS WEIGHT FROM PartsSupplierA.PARTS"/>
<aliases xmi:uuid="mmuuid:06fd8567-3a11-4831-ab41-ca63f486e48b" alias="PARTS">
<aliasedObject href="PartsSupplierA.xmi#mmuuid/a8a006a7-f161-4f3f-9a93-0e82d07842d6"/>
</aliases>
</helper>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:668d1ee1-2fab-40cd-8b05-1b6db9474ab4" outputs="mmuuid/1769ef9d-d6d4-44be-af35-5ef090e1a297">
<inputs href="PartsSupplierA.xmi#mmuuid/a82fa733-bce0-4b20-bb2c-3a8108c091ec"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:3d02e876-80b8-4d35-9eab-440cbc5ba29f" outputs="mmuuid/a905b1d1-859c-4219-a5ac-80159327448a">
<inputs href="PartsSupplierA.xmi#mmuuid/dde8eecd-48b8-4646-8a74-d285aef420b2"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:30966f7a-7e68-4f26-9ff9-67f55da39efd" outputs="mmuuid/1e2023dc-17ee-4c06-9882-f206f6b285dc">
<inputs href="PartsSupplierA.xmi#mmuuid/d26aae8c-c727-4f1d-ba9f-c99b52190a31"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:65d8a48a-2fe8-49ac-9732-459ec02ed2d5" outputs="mmuuid/39ee0028-1e2b-4d37-abc3-50b47233737c">
<inputs href="PartsSupplierA.xmi#mmuuid/753efe1d-ef28-4389-8d24-4fa14c7dd917"/>
</nested>
<inputs href="PartsSupplierA.xmi#mmuuid/a8a006a7-f161-4f3f-9a93-0e82d07842d6"/>
</transformationMappings>
</transformation:TransformationContainer>
{code}
*DESIGNER 8.1 ALPHA 1 PARTS TRANSFORMATION*
{code:xml}
<transformation:TransformationContainer xmi:uuid="mmuuid:faa98ced-0d3a-40a7-afde-37352988a466">
<transformationMappings xsi:type="transformation:SqlTransformationMappingRoot" xmi:uuid="mmuuid:39f8ced6-cc17-4e2d-9d2c-dfa006d58ead" outputs="mmuuid/fa1e3689-242e-4f9b-b1ef-f598be02d3bf" target="mmuuid/fa1e3689-242e-4f9b-b1ef-f598be02d3bf">
<helper xsi:type="transformation:SqlTransformation" xmi:uuid="mmuuid:6e4ead08-bd8c-4719-b283-d976c9574b00">
<nested xsi:type="transformation:SqlTransformation" xmi:uuid="mmuuid:ebea36b9-e6d8-4564-bece-9d3556a45091" selectSql="SELECT * FROM PartsSupplierA.PARTS"/>
<aliases xmi:uuid="mmuuid:9bb6640e-4ec7-4e97-9e39-261ddf670b92" alias="PARTS">
<aliasedObject href="../other_sources/PartsSupplierA.xmi#mmuuid/a8a006a7-f161-4f3f-9a93-0e82d07842d6"/>
</aliases>
</helper>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:cc9d1ffc-1c50-45f3-8bde-e47445461b51" outputs="mmuuid/2a85e933-dfe5-46ca-aec1-619cc2623cc0">
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/a82fa733-bce0-4b20-bb2c-3a8108c091ec"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:522e21d2-897b-47ea-b303-09ef300856f0" outputs="mmuuid/0d15c3f6-5309-4245-8fb2-38384b4d8c37">
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/dde8eecd-48b8-4646-8a74-d285aef420b2"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/a82fa733-bce0-4b20-bb2c-3a8108c091ec"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:2e20a65b-3415-4be7-bc57-5e955b6577e0" outputs="mmuuid/1fbf99b0-d787-4978-b7c3-a63e0fda8d75">
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/dde8eecd-48b8-4646-8a74-d285aef420b2"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/d26aae8c-c727-4f1d-ba9f-c99b52190a31"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/a82fa733-bce0-4b20-bb2c-3a8108c091ec"/>
</nested>
<nested xsi:type="transformation:TransformationMapping" xmi:uuid="mmuuid:23fd17a2-a69f-485b-b4db-28788c4c3aa5" outputs="mmuuid/08109639-899d-4239-a174-6bd35405f021">
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/dde8eecd-48b8-4646-8a74-d285aef420b2"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/d26aae8c-c727-4f1d-ba9f-c99b52190a31"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/753efe1d-ef28-4389-8d24-4fa14c7dd917"/>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/a82fa733-bce0-4b20-bb2c-3a8108c091ec"/>
</nested>
<inputs href="../other_sources/PartsSupplierA.xmi#mmuuid/a8a006a7-f161-4f3f-9a93-0e82d07842d6"/>
</transformationMappings>
</transformation:TransformationContainer>
{code}
--
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-1611) Add action to copy models from a VDB into your workspace project
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1611?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-1611:
--------------------------------------
Assignee: Barry LaFond
> Add action to copy models from a VDB into your workspace project
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1611
> URL: https://issues.jboss.org/browse/TEIIDDES-1611
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Editors, VDB & Execution
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> TEIIDDES-505 covered most of the refactoring issues with models in a workspace/project. However, the remaining use-case of importing a VDB into a project and trying to work with it has not been covered yet.
> This feature would provide a means to extract/copy contents of a VDB and construct a corresponding file structure of folders/models within the VDB. This would be a "reverse-synch" methodology and allow users to use VDBs as a starting point for their modeling as well as the "ending point".
--
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-853) Teiid artifacts should respond more gracefully to Teiid project refactoring
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-853?page=com.atlassian.jira.plug... ]
Barry LaFond resolved TEIIDDES-853.
-----------------------------------
Release Notes Text: After renaming project in Designer's Model Explorer (or other project explorer) validation warnings will exist in the VDBs. Right-clicking the warnings and using "Quick Fix" will show "Synchronize VDB" fix which will tweak the model paths referenced in the VDBs to remove the warnings.
Resolution: Done
Done
> Teiid artifacts should respond more gracefully to Teiid project refactoring
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-853
> URL: https://issues.jboss.org/browse/TEIIDDES-853
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.2
> Environment: RHEL, JBDS jbdevstudio-linux-gtk-4.0.0.v201012070137R-H33-Beta2.jar, SOA-P 5.1 ER5, Teiid 7.2
> Reporter: Brian Fitzpatrick
> Assignee: Dan Florian
> Priority: Critical
> Fix For: 8.1
>
>
> While I was trying to figure things out with the Virtual Procedures test script, I received a newer copy of the Parts Project from Barry that included the data files for loading the database tables. As a result, I wanted to change the name of the Teiid Model Project that I had created for the test.
> Though the Teiid Designer Perspective (via the Model Explorer view) doesn't allow you to rename a project, I popped over to a different perspective (the Java EE Perspective) and renamed the project there. I was then able to import Barry's project and take a look.
> Well, I didn't realize that the VDB file (and potentially others) was hardwired to the project name as part of the path to the .xmi files. So that threw me into several problems I had to resolve. Eventually I did resolve them, but we need to provide some sort of refactoring capabilities for Teiid projects and respond to those changes more gracefully.
--
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-853) Teiid artifacts should respond more gracefully to Teiid project refactoring
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-853?page=com.atlassian.jira.plug... ]
Barry LaFond commented on TEIIDDES-853:
---------------------------------------
Checked in fix : https://github.com/Teiid-Designer/teiid-designer/commit/1b7f6a24ff40c0344...
* relaxed RefactorAction enablement to allow renaming Projects
* added setEnabledState() override method in MoveRefactorAction to allow moving VDBs
> Teiid artifacts should respond more gracefully to Teiid project refactoring
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-853
> URL: https://issues.jboss.org/browse/TEIIDDES-853
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 7.2
> Environment: RHEL, JBDS jbdevstudio-linux-gtk-4.0.0.v201012070137R-H33-Beta2.jar, SOA-P 5.1 ER5, Teiid 7.2
> Reporter: Brian Fitzpatrick
> Assignee: Dan Florian
> Priority: Critical
> Fix For: 8.1
>
>
> While I was trying to figure things out with the Virtual Procedures test script, I received a newer copy of the Parts Project from Barry that included the data files for loading the database tables. As a result, I wanted to change the name of the Teiid Model Project that I had created for the test.
> Though the Teiid Designer Perspective (via the Model Explorer view) doesn't allow you to rename a project, I popped over to a different perspective (the Java EE Perspective) and renamed the project there. I was then able to import Barry's project and take a look.
> Well, I didn't realize that the VDB file (and potentially others) was hardwired to the project name as part of the path to the .xmi files. So that threw me into several problems I had to resolve. Eventually I did resolve them, but we need to provide some sort of refactoring capabilities for Teiid projects and respond to those changes more gracefully.
--
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 resolved TEIIDDES-505.
-----------------------------------
Release Notes Text: When models are refactored (renamed or moved) in a project, new validation warnings are created if the refactored model is contained in one or more VDBs. A Quick Fix action is available which will synchronize a VDB and remove those warnings.
Resolution: Done
> 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-1611) Add action to copy models from a VDB into your workspace project
by Barry LaFond (JIRA)
Barry LaFond created TEIIDDES-1611:
--------------------------------------
Summary: Add action to copy models from a VDB into your workspace project
Key: TEIIDDES-1611
URL: https://issues.jboss.org/browse/TEIIDDES-1611
Project: Teiid Designer
Issue Type: Feature Request
Components: Editors, VDB & Execution
Affects Versions: 8.1
Reporter: Barry LaFond
Fix For: 8.1
TEIIDDES-505 covered most of the refactoring issues with models in a workspace/project. However, the remaining use-case of importing a VDB into a project and trying to work with it has not been covered yet.
This feature would provide a means to extract/copy contents of a VDB and construct a corresponding file structure of folders/models within the VDB. This would be a "reverse-synch" methodology and allow users to use VDBs as a starting point for their modeling as well as the "ending point".
--
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-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