[
https://issues.jboss.org/browse/TEIIDDES-2034?page=com.atlassian.jira.plu...
]
Barry LaFond resolved TEIIDDES-2034.
------------------------------------
Resolution: Done
Done
Inconsistent model naming validation in wizards and dialogs
-----------------------------------------------------------
Key: TEIIDDES-2034
URL:
https://issues.jboss.org/browse/TEIIDDES-2034
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 8.3, 8.3.1
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 8.4
Performed an analysis of Designer's dialog and wizard panels validation of editable
model names:
1) Refactor > Rename (*OK*)
- Seems to allow only LETTERS, NUMBERS and '_' char
- Shows appropriate error message
2) New Model Wizard (*FIX*)
- Model name allows any char
3) Flat File and XML Import Wizards (*FIX*)
- Source and View model names allow any char
- View Table name only allows LETTERS, NUMBERS and '_' char
4) Import > WSDL File or URL >> Source and View Model (SOAP) (*FIX*)
- Source and View model names allow any char
5) Import > WSDL File or URL >> Web Service Model (*FIX*)
- Web Service Model Name allows any char (first page)
- Schema model name allows any char (Workspace Location Selection page)
- XML model name allows any char (last page)
6) JDBC Import wizard Model Name allows any char (*FIX*)
7) DDL Import Wizard (*OK*)
- Appears to be working correctly: Allows only LETTERS, NUMBERS and '_' char
8) Import > Designer Test File >> Source or View Models (*FIX*)
- Source and View model names allow any char
- Utilizes Relational Model Selector dialog
- Als used in "Create Materailized View Model" dialog
9) Create Web Service dialog (*FIX*)
- schema and WS model names allow any char
10) Modeling > Create XML View Documents (*FIX*)
- Select or create XML View model dialog allow any char for New Model Name
- Similar to Relational Model Selector dialog
11) Import > Teiid Connection >> Source Model (*FIX*)
- Source model name allows any char
--
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