[JBoss JIRA] Created: (TEIIDDES-622) Refactor > Move Virtual model with diagram references to source tables in other folders results in errors
by Barry LaFond (JIRA)
Refactor > Move Virtual model with diagram references to source tables in other folders results in errors
---------------------------------------------------------------------------------------------------------
Key: TEIIDDES-622
URL: https://jira.jboss.org/browse/TEIIDDES-622
Project: Teiid Designer
Issue Type: Bug
Components: Diagrams, Modeling
Reporter: Barry LaFond
Fix For: 7.1.1
Created an Error problem marker (and accompanying error message) after Refactor > Move action of a Virtual model to a folder under a project
1) Create Relational Model with Table
2) Create Virtual Model.
3) In Virtual model, create Custom Diagram
4) Open new custom diagram and add Relational model to it
5) Save all models
6) Create Folder under project (Top)
7) Create Folder under Top folder (Bottom)
8) Refactor > Move Relational model to Bottom folder
9) Refacor > Move Virtual model to TOp folder
10) Save all and should see both error and Problem Error
--
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
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-540) Refactoring/Move view model dependant upon other view models gets errors since other view models didn't move
by Paul Nittel (JIRA)
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
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-599) org.teiid.designer.datatools unnecessary dependencies
by Mark Addleman (JIRA)
org.teiid.designer.datatools unnecessary dependencies
-----------------------------------------------------
Key: TEIIDDES-599
URL: https://jira.jboss.org/browse/TEIIDDES-599
Project: Teiid Designer
Issue Type: Patch
Components: Eclipse Integration
Affects Versions: 7.1
Environment: eclipse
Reporter: Mark Addleman
We are planning to embed parts of the Designer to programmatically construct VDB files. As such, we prefer to limit dependencies as much as possible. The org.teiid.designer.datatools bundle unnecessarily declares a few dependencies which I've cleaned up in the patch below. To us, the most important unnecessary dependency is org.eclipse.ui
Index: META-INF/MANIFEST.MF
===================================================================
--- META-INF/MANIFEST.MF (revision 959)
+++ META-INF/MANIFEST.MF (working copy)
@@ -6,16 +6,12 @@
Bundle-Activator: org.teiid.designer.datatools.DatatoolsPlugin
Bundle-Vendor: %providerName
Bundle-Localization: plugin
-Require-Bundle: org.eclipse.ui,
- org.eclipse.core.runtime,
- org.teiid.core.designer,
+Require-Bundle: org.teiid.core.designer,
org.eclipse.core.runtime.compatibility,
teiid_embedded_query,
org.teiid.designer.core,
- org.teiid.designer.jdbc,
org.eclipse.datatools.connectivity,
- org.eclipse.core.resources,
- org.teiid.designer.metamodels.core
+ org.eclipse.core.resources
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Export-Package: org.teiid.designer.datatools,
--
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
14 years, 3 months
[JBoss JIRA] Created: (TEIIDDES-627) File > Save As action results in validation errors in new model if model is virtual and folder location different than original location.
by Barry LaFond (JIRA)
File > Save As action results in validation errors in new model if model is virtual and folder location different than original location.
-----------------------------------------------------------------------------------------------------------------------------------------
Key: TEIIDDES-627
URL: https://jira.jboss.org/browse/TEIIDDES-627
Project: Teiid Designer
Issue Type: Bug
Components: Modeling
Affects Versions: 7.1, 7.0
Reporter: Barry LaFond
Priority: Minor
Fix For: 8.0
The ModelCopyCommand class doesn't take into account the possibility in having a destination folder different than the original model.
The Action will perform the Save As OK, however, there may be validation errors due to unresolved Imports and Objects
By selecting the model and Rebuilding Imports, the validation errors should get fixed.
There may be Criteria errors if the SQL contains the full path/model name. users will need to re-edit the Criteria to fix it.
The elegant fix would be to :
1) Perform a rebuildImports() action during the command execution
2) determine the relative path change due to different destinations and perform an HRef update (SEE ResourceMoveCommand)
3) Perform an update to the Criteria via RefactorModelExtensionManager framework. (i.e. MappingRefactorModelHandler)
--
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
14 years, 3 months