July 2013 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1756) web service generator get stuck

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1756?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1756. --------------------------------- Resolution: Cannot Reproduce Bug Marking as not reproducible. Will reopen if this crops up again. > web service generator get stuck > ------------------------------- > > Key: TEIIDDES-1756 > URL: https://issues.jboss.org/browse/TEIIDDES-1756 > Project: Teiid Designer > Issue Type: Bug > Components: Web Services Support > Affects Versions: 8.1 > Environment: windows XP > Reporter: luca gioppo > Assignee: Ted Jones > Fix For: 8.2 > > Attachments: .log, .log, eclipse.png, saveus.zip > > > After invoking the web service generation the operation get stuck (this did not happen in 7.x version, but generation of WS was not so good anyway) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1642) WAR Generator Excludes Input/Output Schemas When Workspace Location Includes Spaces (Windows Only)

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1642?page=com.atlassian.jira.plu... ] Ted Jones updated TEIIDDES-1642: -------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/pull/195 > WAR Generator Excludes Input/Output Schemas When Workspace Location Includes Spaces (Windows Only) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1642 > URL: https://issues.jboss.org/browse/TEIIDDES-1642 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.7 > Environment: Windows > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > The schema files are not included in generated WAR files if the workspace location has spaces in it. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1642) WAR Generator Excludes Input/Output Schemas When Workspace Location Includes Spaces (Windows Only)

by Ted Jones (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1642?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1642. --------------------------------- Resolution: Done Schema resources were not resolved (when comparing to VDB resources) due to spaces in workspace. Replaced spaces with "%20" in comparison string. > WAR Generator Excludes Input/Output Schemas When Workspace Location Includes Spaces (Windows Only) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1642 > URL: https://issues.jboss.org/browse/TEIIDDES-1642 > Project: Teiid Designer > Issue Type: Feature Request > Components: Web Services Support > Affects Versions: 7.7 > Environment: Windows > Reporter: Ted Jones > Assignee: Ted Jones > Fix For: 8.2 > > > The schema files are not included in generated WAR files if the workspace location has spaces in it. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1770) Add Teiid Connection importer timeout to preferences

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1770?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1770. ------------------------------------- Resolution: Done Timeout was added to the preferences, so that user can extend the default if necessary. https://github.com/Teiid-Designer/teiid-designer/pull/194 > Add Teiid Connection importer timeout to preferences > ---------------------------------------------------- > > Key: TEIIDDES-1770 > URL: https://issues.jboss.org/browse/TEIIDDES-1770 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.2 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > Currently the Teiid Connection importer allows a 2min timeout for the dynamic vdb to deploy and the metadata to load. This should be user-configurable via preferences. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1706) During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1706?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1706. ------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) Resolution: Done No longer an issue after refactoring of the DDL framework. Retested OK. > During DDL re-import the MergeProcessorImpl processes the ModelAnnotationImpl but misses key properties > ------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1706 > URL: https://issues.jboss.org/browse/TEIIDDES-1706 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Blocker > Fix For: 8.2 > > > MergeProcessorImpl.doOrderContained() shows the following for source and result ModelAnnotationImpl. > ProducerName and ProducerVersion are lost. > sourceObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@30298bbf (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: Teiid Designer, ProducerVersion: 8.2.0) > resultObject: > org.teiid.designer.metamodels.core.impl.ModelAnnotationImpl@d3b11c3 (description: null, nameInSource: null, primaryMetamodelUri: http://www.metamatrix.com/metamodels/Relational, modelType: PHYSICAL, maxSetSize: 0, visible: true, supportsDistinct: true, supportsJoin: true, supportsOrderBy: true, supportsOuterJoin: true, supportsWhereAll: true, namespaceUri: null, ProducerName: null, ProducerVersion: null) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1705) Model imported from DDL is missing relational model extension MED

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1705?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1705. ------------------------------------- Resolution: Done Verified that the Relational MED is added to the model, retested ok. > Model imported from DDL is missing relational model extension MED > ----------------------------------------------------------------- > > Key: TEIIDDES-1705 > URL: https://issues.jboss.org/browse/TEIIDDES-1705 > Project: Teiid Designer > Issue Type: Bug > Components: Extension Framework > Affects Versions: 8.1 > Reporter: Barry LaFond > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.2 > > > While working on TEIIDDES-1660 noticed that if I re-imported to same model an NPE showed up because the relational MED was not saved in the model. > RelationalPlugin is responding to a New Model event and applying the MED, but later in the importer, the model contents is copied and it loses the MED. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1670) DDL Importer - problem with re-import when setting descriptions

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1670?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1670. ------------------------------------- Assignee: Mark Drilling (was: Paul Richardson) Resolution: Done This retests ok, after recent changes to the importer. > DDL Importer - problem with re-import when setting descriptions > --------------------------------------------------------------- > > Key: TEIIDDES-1670 > URL: https://issues.jboss.org/browse/TEIIDDES-1670 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Priority: Critical > Fix For: 8.2 > > > When using the DDL importer for an existing model (update), the model entity names are getting reset. This only seems to occur if 'set description of Model Entities to corresponding DDL statement' checkbox is checked. The Entity names get changed to the default name of the entity. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1457) ERROR: SYSADMIN.logMsg does not exist.

by Hisanobu Okuda (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1457?page=com.atlassian.jira.plu... ] Hisanobu Okuda reassigned TEIIDDES-1457: ---------------------------------------- Assignee: Hisanobu Okuda > ERROR: SYSADMIN.logMsg does not exist. > -------------------------------------- > > Key: TEIIDDES-1457 > URL: https://issues.jboss.org/browse/TEIIDDES-1457 > Project: Teiid Designer > Issue Type: Bug > Components: Testing > Affects Versions: 7.7 > Environment: Windows 7 64 bits > Reporter: Mónica L.A. > Assignee: Hisanobu Okuda > Fix For: 7.7.3 > > > I've just put different calls to SYSADMIN.logMsg to trace a procedure and when I save, the transformation editor show the message: ERROR: SYSADMIN.logMsg does not exist -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1654) DDL Importer needs to better handle constraint naming in generated model

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1654?page=com.atlassian.jira.plu... ] Mark Drilling resolved TEIIDDES-1654. ------------------------------------- Resolution: Done The ModeShape DDL sequencer is now handling the unique naming of constraints. Resolved another issue with UniqueConstraint generation. pull request https://github.com/Teiid-Designer/teiid-designer/pull/193 > DDL Importer needs to better handle constraint naming in generated model > ------------------------------------------------------------------------ > > Key: TEIIDDES-1654 > URL: https://issues.jboss.org/browse/TEIIDDES-1654 > Project: Teiid Designer > Issue Type: Enhancement > Components: Import/Export > Affects Versions: 8.1 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.2 > > > When importing DDL, the generated model can have errors when multiple constraints are present. For example the following DDL: > CREATE FOREIGN TABLE G1( e1 integer, e2 varchar, e3 date, PRIMARY KEY (e1, e2), INDEX(e2, e3), ACCESSPATTERN(e1), UNIQUE(e1), ACCESSPATTERN(e2, e3)) > includes two access patterns which end up being named the same. The importer should auto increment the names to avoid name conflicts. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1776) Deleting only server instance does not remove server definition text (mm://localost:9999) in Default Teiid Server section in Model Explorer

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1776: -------------------------------------- Summary: Deleting only server instance does not remove server definition text (mm://localost:9999) in Default Teiid Server section in Model Explorer Key: TEIIDDES-1776 URL: https://issues.jboss.org/browse/TEIIDDES-1776 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration, Views Affects Versions: 8.2 Reporter: Barry LaFond Assignee: Paul Richardson Fix For: 8.2 Deleted only server and Default Teiid Server still says: mm://localhost:9999 -- 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, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2013