[JBoss JIRA] (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)
[ https://issues.jboss.org/browse/TEIIDDES-627?page=com.atlassian.jira.plug... ]
Barry LaFond reassigned TEIIDDES-627:
-------------------------------------
Assignee: Dan Florian
> 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://issues.jboss.org/browse/TEIIDDES-627
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.0, 7.1
> Reporter: Barry LaFond
> Assignee: Dan Florian
> Priority: Minor
> Fix For: 8.1
>
>
> 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, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (TEIIDDES-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-1436:
--------------------------------------
Assignee: Ted Jones
> Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1436
> URL: https://issues.jboss.org/browse/TEIIDDES-1436
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Ted Jones
> Assignee: Ted Jones
> Fix For: 8.1
>
> Attachments: foo.zip
>
>
> "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH
--
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
12 years, 11 months
[JBoss JIRA] (TEIIDDES-1388) Improve Flat File importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1388?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-1388:
--------------------------------------
Assignee: Barry LaFond
> Improve Flat File importer
> --------------------------
>
> Key: TEIIDDES-1388
> URL: https://issues.jboss.org/browse/TEIIDDES-1388
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Affects Versions: 7.7, 7.7.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: 8.1
>
>
> The Flat File importer still lacks simplicity. Need to spend another cycle improving usability
> PAUL NITTEL wrote:
> I'm tinkering with this thing and have a few suggestions. (The problem with coming up with cool wizardly things is they spark other synapses thereby creating an endless flow of work.)
> The Create Teiid Flat File Connection action seems to be a mixture of building the data source connection and laying the groundwork for the transformation (like where are the column name and types). Moving this to the Create Source Model wizard might make it easier and flow better for the user.
> Rather than checkboxes that presume much about how flat file data may be constructed, how about allowing the user to tell you which lines are contain heading and type info (if any, of course)? In the case of my weird data file, there a comment in line 1, line 2 is blank, line 3 have column names and line 4 has types. Data starts in line 5.
> I realize my case is atypical, but might be worth consideration. ;-)
--
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
12 years, 11 months