[
https://issues.jboss.org/browse/TEIIDDES-1703?page=com.atlassian.jira.plu...
]
Barry LaFond updated TEIIDDES-1703:
-----------------------------------
Fix Version/s: 8.2
Description:
The new Refactor logic utilizes Eclipse's refactor/preview framework. Works GREAT.
Problem is, unlike deleting folders and projects, deleting a model will result in the
default behavior of deleting any and all dependent models. For a WS model, this may
include XSD files, XML Files and Source models.
Users can click "Preview>>" to view and deselect items for deletion, but
this operation is probably NOT for the faint of heart.
Suggest maybe adding some verbage/warning on the FIRST page of the wizard so user knows
that DEPENDENT files will be deleted.
Maybe add a "check-box" to change the default behavior to NOT delete dependent
models.
Affects Version/s: 8.2
Component/s: Modeling
Delete Model action default behavior is to delete all dependent
models and probably not what users expects. Re-visit use-case
-----------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1703
URL:
https://issues.jboss.org/browse/TEIIDDES-1703
Project: Teiid Designer
Issue Type: Enhancement
Components: Modeling
Affects Versions: 8.2
Reporter: Barry LaFond
Fix For: 8.2
The new Refactor logic utilizes Eclipse's refactor/preview framework. Works GREAT.
Problem is, unlike deleting folders and projects, deleting a model will result in the
default behavior of deleting any and all dependent models. For a WS model, this may
include XSD files, XML Files and Source models.
Users can click "Preview>>" to view and deselect items for deletion, but
this operation is probably NOT for the faint of heart.
Suggest maybe adding some verbage/warning on the FIRST page of the wizard so user knows
that DEPENDENT files will be deleted.
Maybe add a "check-box" to change the default behavior to NOT delete dependent
models.
--
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