[JBoss JIRA] (TEIIDDES-1147) Create Model Extension Definition Resource Validation Rules
by Dan Florian (Created) (JIRA)
Create Model Extension Definition Resource Validation Rules
-----------------------------------------------------------
Key: TEIIDDES-1147
URL: https://issues.jboss.org/browse/TEIIDDES-1147
Project: Teiid Designer
Issue Type: Task
Components: Validation
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 7.6
Validation rules need to be created for when MEDs are saved. These rules will run when a build is run. We may need to create our own builder also. Validation rules should exist for at least the following:
1. when a model contains a different version of a MED than the one in the registry (high priority)
2. when a model contains a MED that is not found in the registry (high priority)
3. move current problem marker creation out of MED Editor and into a validation rule (high priority)
3. when a model object has an extension property but does not have the MED stored in its model (low priority)
4. when a model object has an extension property that is not found in the corresponding MED (low priority)
5. any others that are needed
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (TEIIDDES-1140) Model Extension Definition Validation Should Report All Validation Messages And Stop Stop When It Finds The First Error
by Dan Florian (Created) (JIRA)
Model Extension Definition Validation Should Report All Validation Messages And Stop Stop When It Finds The First Error
-----------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-1140
URL: https://issues.jboss.org/browse/TEIIDDES-1140
Project: Teiid Designer
Issue Type: Task
Components: Editors
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 8.0
The validation being done associated with MEDs is being done by the ModelExtensionDefinitionValidator. While the validator does perform validation in lots of different areas and reports issues in each of those areas, it does not report multiple issues within the same category. For instance, when the validator looks at all property definitions, it will only report the first error it finds in any of the property definitions. It should report all the problems from all the property definitions. Need to update ValidationStatus class so that it can contain multiple statuses and update the validator to report multiple statuses.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (TEIIDDES-1151) Model Extension Definition Version History Should Be Persisted Along With The Registry
by Dan Florian (Created) (JIRA)
Model Extension Definition Version History Should Be Persisted Along With The Registry
--------------------------------------------------------------------------------------
Key: TEIIDDES-1151
URL: https://issues.jboss.org/browse/TEIIDDES-1151
Project: Teiid Designer
Issue Type: Task
Components: Modeling
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 8.0
Persisting a version history of MED stored in the registry will help determine if the MED the user wants to register is newer or older than the one in already in the registry. The MED business object does have a version number but there are problems with using that to determine if one MED is newer/older than another MED. For instance, in a multi-user environment the same MED could be updated by different users. Each user could end up with a MED with the same version but with different content. And those MEDs could end up in the hands of other users who could also create new versions. Of course an enterprise could be diligent about controlling MED versioning using their own version-control system and possibly get around this issue. With that said, persisting a MED version history by using something like a checksum/sha-1 would remove the problems associated with relying on the version number at least for a workspace. We might also look at writing an exporter/importer to export the version history and then import into another workspace.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months
[JBoss JIRA] (TEIIDDES-1150) Model Extension Definition Problem Markers For Models Should Support Quick Fix
by Dan Florian (Created) (JIRA)
Model Extension Definition Problem Markers For Models Should Support Quick Fix
------------------------------------------------------------------------------
Key: TEIIDDES-1150
URL: https://issues.jboss.org/browse/TEIIDDES-1150
Project: Teiid Designer
Issue Type: Enhancement
Components: Editors
Affects Versions: 7.6
Reporter: Dan Florian
Assignee: Dan Florian
Fix For: 8.0
Model problem markers related to MEDs should have a quick fix option. Currently there are 2 MED problem markers:
(1) MED found in model is not registry. Quick fix should offer to save that MED to a file in the workspace.
(2) MED found in model is different than the same MED in the registry. Quick fix should offer to update the model to the registry copy of the MED.
I'm thinking that the quick fix in each case would not offer to fix all markers of the same error at the same time. However, the quick fix for (1) could offer to save all MEDs in a common directory. And the quick fix for (2) could offer to update all models to the MED version. These options might be nice and deserve more thought.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 5 months