[
https://jira.jboss.org/browse/TEIIDDES-540?page=com.atlassian.jira.plugin...
]
Paul Nittel commented on TEIIDDES-540:
--------------------------------------
A couple observations: After completing the refactoring there are no validation errors,
however the VDB cannot synch its contents since they are not found in their original
locations. The server renamed the data sources to include the new paths.
Refactoring/Move view model dependant upon other view models gets
errors since other view models didn't move
------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-540
URL:
https://jira.jboss.org/browse/TEIIDDES-540
Project: Teiid Designer
Issue Type: Bug
Components: Validation
Affects Versions: 7.1
Environment: Fedora 12, Designer 7.1 M1
Reporter: Paul Nittel
Attachments: LogWithRefactorErrors.log
After importing from JDBC, I created view models atop each of the 3 imported models. I
then created another view model wihch used the first set of models.
vParts <-- vPartsO, vPartsS, vPartsM
I created a series of folder into which I began to refactor the models. Source models
refactored w/o issue. I refactored vParts and then received errors that the other models
couldn't be found in vParts' new folder. (Unresolved reference
"file:/home/pnittel/workspace-T71M1/HotMonday/View/Relational/vPartsM.xmi -- in this
case, it's still in HotMonday/)
The Message Log shows other errors, at least one of which had a stack trace. I'll
attach the log
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira