[
https://issues.jboss.org/browse/TEIIDDES-1225?page=com.atlassian.jira.plu...
]
Dan Florian resolved TEIIDDES-1225.
-----------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Release Notes Text: It is no longer possible to try and add/update a *.mxd file
with errors to the registry.
Resolution: Done
Before adding or updating MED in registry, first the problem markers are checked, if there
is no problem markers then the MED is parsed to see if there are parse errors. This is a
redundant check if the user is building automatically on save, but if not auto building
this check is necessary. I could not find a way to check to see if a file is in need of
building.
'Add MED to Registry' action allows attempt to add an invalid
MED to the registry
---------------------------------------------------------------------------------
Key: TEIIDDES-1225
URL:
https://issues.jboss.org/browse/TEIIDDES-1225
Project: Teiid Designer
Issue Type: Bug
Components: Extension Framework
Affects Versions: 7.7
Reporter: Mark Drilling
Assignee: Dan Florian
Fix For: 7.7
The 'Add MED to Registry' action looks at the mxd problem markers before doing
the add operation. However, if the workspace has not been built the file may not have a
problem marker. This results in attempt to add an invalid MED to the registry. We should
not allow the process to get that far - ensure the build is complete or check for errors
in a different manner.
Example usage is in ModelExtensionDefinitionEditor.createActions, which uses
RegistryDeploymentValidator.checkProblemMarkers to do this check currently.
--
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