July 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1372) Mass format the codebase

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1372: ----------------------------------------- Summary: Mass format the codebase Key: TEIIDDES-1372 URL: https://issues.jboss.org/browse/TEIIDDES-1372 Project: Teiid Designer Issue Type: Task Reporter: Paul Richardson Assignee: Paul Richardson Priority: Minor Fix For: 8.0 Mass format the codebase to conform to a single formatting standard. This will ensure that a migration to git will minimize commit patch confusion. -- 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

13 years, 1 month

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1415) Request Procedure Generated Namespace Is Incorrect For Element

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1415: ------------------------------------- Summary: Request Procedure Generated Namespace Is Incorrect For Element Key: TEIIDDES-1415 URL: https://issues.jboss.org/browse/TEIIDDES-1415 Project: Teiid Designer Issue Type: Bug Affects Versions: 7.7.1 Reporter: Dan Florian Assignee: Ted Jones Fix For: 8.0 I ran the "WSDL to Source and View Model (SOAP)" importer using the US States WSDL. The importer generated the source and view models. Running a preview data on the GetStateInfo procedure fails. The GetStateInfo_request generated code is this: SELECT XMLELEMENT(NAME GetStateInfo, XMLNAMESPACES(DEFAULT 'http://www.teiid.org/stateService/'), XMLELEMENT(NAME stateCode, stateServiceView.GetStateInfo_request.stateCode)) AS xml_out; Changing to this corrected the problem: SELECT XMLELEMENT(NAME GetStateInfo, XMLNAMESPACES(DEFAULT ''), XMLELEMENT(NAME stateCode, stateServiceView.GetStateInfo_request.stateCode)) AS xml_out; -- 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

13 years, 1 month

3
6
0 / 0

[JBoss JIRA] (TEIIDDES-1462) Function overloading is not working with Source Function feature

by Debbie Steigner (JIRA)

Debbie Steigner created TEIIDDES-1462: ----------------------------------------- Summary: Function overloading is not working with Source Function feature Key: TEIIDDES-1462 URL: https://issues.jboss.org/browse/TEIIDDES-1462 Project: Teiid Designer Issue Type: Bug Components: Validation Affects Versions: 7.4 Reporter: Debbie Steigner I am trying to migrate the UDF functions that we have in MetaMatrix 5.5.4 into EDS and found an issue with Function overloading is not working with Source Function feature. For example, we have GREATEST oracle source function with signature as shown below. GREATEST (expr1 timestamp, expr2 timestamp) RETURN timestamp; GREATEST (expr1 integer, expr2 integer) RETURN integer; But designer throws an error "The name GREATEST is the same (ignoring case) as 1 other object(s) under the same parent" as shown in the attached screenshot. -- 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

13 years, 1 month

3
3
0 / 0

[JBoss JIRA] (TEIIDDES-1458) Import of DDL with Foreign Keys Fails.

by Steve Darnowsky (JIRA)

Steve Darnowsky created TEIIDDES-1458: ----------------------------------------- Summary: Import of DDL with Foreign Keys Fails. Key: TEIIDDES-1458 URL: https://issues.jboss.org/browse/TEIIDDES-1458 Project: Teiid Designer Issue Type: Bug Reporter: Steve Darnowsky -- 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

13 years, 1 month

3
4
0 / 0

[JBoss JIRA] (TEIIDDES-1348) Investigate Adding Additional VDB Properties

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1348: ----------------------------------- Summary: Investigate Adding Additional VDB Properties Key: TEIIDDES-1348 URL: https://issues.jboss.org/browse/TEIIDDES-1348 Project: Teiid Designer Issue Type: Enhancement Components: VDB & Execution Affects Versions: 7.7 Reporter: Ted Jones Fix For: 8.0 We currently allow the user to set the query timeout on the VDB. We had a request from the field to see if there were other properties we could set at that level and add to the tab. -- 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

13 years, 1 month

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1452) Unable to install

by Steve Darnowsky (JIRA)

Steve Darnowsky created TEIIDDES-1452: ----------------------------------------- Summary: Unable to install Key: TEIIDDES-1452 URL: https://issues.jboss.org/browse/TEIIDDES-1452 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 7.7 Environment: teiid designer 7.7, eclipse 3.7.2 Reporter: Steve Darnowsky Using Teiid designer 7.7 plug in in Eclipse 3.7.2. Created soruce model and then imported DDL. Selected import wsdl into source model procedure. Created connection profile that points to url for WSDL.Changed Source Model created in previous step. Status - "Existing model xxxx.xmi has connection profile for different wsdl. Continued to to next dialog. In the Procedure Defintion dialog added element name in Schema Contents window. Invalid Name error displayed - "The character "-" is not allowed...." Is there a workaround for the name restrictions? Also why is this status message displayed when I select an existing model in soruce definition dialog? If I select the radio button to generate legacy create and extract functions, the import completes successfully. -- 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

13 years, 1 month

4
6
0 / 0

[JBoss JIRA] (TEIIDDES-1326) Use findbugs to identify code bugs and potential problems

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1326: ----------------------------------------- Summary: Use findbugs to identify code bugs and potential problems Key: TEIIDDES-1326 URL: https://issues.jboss.org/browse/TEIIDDES-1326 Project: Teiid Designer Issue Type: Task Reporter: Paul Richardson Fix For: 8.0, Future Use the findbugs eclipse plugin to identify and fix potential coding problems and bugs. At creation of this issue, findbugs reports ~200 potential problems with the codebase, ranging from troubling - scariest. Some are false-positives but some do point to potential problems. Consider each one and fix if required. -- 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

13 years, 1 month

4
5
0 / 0

[JBoss JIRA] Created: (TEIIDDES-595) ModelAnnotations Are Created When Models Are Deleted

by Dan Florian (JIRA)

ModelAnnotations Are Created When Models Are Deleted ---------------------------------------------------- Key: TEIIDDES-595 URL: https://jira.jboss.org/browse/TEIIDDES-595 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Reporter: Dan Florian Just selected a model in the Model Explorer and deleted it. I noticed that the ModelAnnotationImpl constructor was being called when the model was being deleted. This doesn't seem right but doesn't seem to affect anything. Here is the stack trace: Daemon Thread [Thread-0] (Suspended (breakpoint at line 389 in ModelAnnotationImpl)) ModelAnnotationImpl.<init>() line: 389 CoreFactoryImpl.createModelAnnotation() line: 127 CoreFactoryImpl.create(EClass) line: 53 MtkXmiHelper(XMLHelperImpl).createObject(EFactory, EClassifier) line: 891 MtkXmiHandler.createObjectFromFactory(EFactory, String) line: 161 MtkXmiHandler.createTopObject(String, String) line: 192 MtkXmiHandler(XMLHandler).processElement(String, String, String) line: 1019 MtkXmiHandler(XMIHandler).processElement(String, String, String) line: 87 MtkXmiHandler(XMLHandler).startElement(String, String, String) line: 1001 MtkXmiHandler.startElement(String, String, String) line: 769 MtkXmiHandler(XMLHandler).startElement(String, String, String, Attributes) line: 712 MtkXmiHandler(XMIHandler).startElement(String, String, String, Attributes) line: 169 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).startElement(QName, XMLAttributes, Augmentations) line: 501 XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanStartElement() line: 1363 XMLDocumentScannerImpl$ContentDriver(XMLDocumentFragmentScannerImpl$FragmentContentDriver).next() line: 2755 XMLDocumentScannerImpl.next() line: 648 XMLDocumentScannerImpl(XMLDocumentFragmentScannerImpl).scanDocument(boolean) line: 511 XIncludeAwareParserConfiguration(XML11Configuration).parse(boolean) line: 808 XIncludeAwareParserConfiguration(XML11Configuration).parse(XMLInputSource) line: 737 SAXParserImpl$JAXPSAXParser(XMLParser).parse(XMLInputSource) line: 119 SAXParserImpl$JAXPSAXParser(AbstractSAXParser).parse(InputSource) line: 1205 SAXParserImpl$JAXPSAXParser.parse(InputSource) line: 522 SAXParserImpl(SAXParser).parse(InputSource, DefaultHandler) line: 395 MtkXmiResourceLoader(XMLLoadImpl).load(XMLResource, InputStream, Map<?,?>) line: 181 MtkXmiResourceImpl.doLoad(InputStream, Map) line: 282 MtkXmiResourceImpl(ResourceImpl).load(InputStream, Map<?,?>) line: 1494 MtkXmiResourceImpl(ResourceImpl).load(Map<?,?>) line: 1282 MtkXmiResourceImpl.load(Map) line: 222 ModelBufferImpl.open(IProgressMonitor) line: 236 ModelResourceImpl.openBuffer(IProgressMonitor) line: 434 ModelResourceImpl(OpenableImpl).getBuffer() line: 381 ModelResourceImpl.refreshIndexType() line: 247 ModelWorkspaceManager$NotificationProcessor.refreshResourceIndexType(Object) line: 1162 ModelWorkspaceManager$NotificationProcessor.checkResourceForIndexing(Notification) line: 1137 ModelWorkspaceManager$NotificationProcessor.notifyChanged(Notification) line: 1151 ChangeNotifier.fireNotifyChanged(Notification) line: 51 UnitOfWorkImpl.commit() line: 251 ModelerCore.commitTxn() line: 356 DeleteResourceAction.closeResources(List) line: 324 DeleteResourceAction.doRun() line: 381 AbstractAction$1.run() line: 537 BusyIndicator.showWhile(Display, Runnable) line: 70 DeleteResourceAction(AbstractAction).run() line: 540 DeleteResourceAction(Action).runWithEvent(Event) line: 498 -- 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

13 years, 2 months

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-1438) Canceling New Project Wizard Should Cancel Follow-On Wizard

by Dan Florian (JIRA)

Dan Florian created TEIIDDES-1438: ------------------------------------- Summary: Canceling New Project Wizard Should Cancel Follow-On Wizard Key: TEIIDDES-1438 URL: https://issues.jboss.org/browse/TEIIDDES-1438 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.8 Environment: OS X 10.7.4, Teiid Designer 7.8, Eclipse Indigo Release 2 Reporter: Dan Florian In a brand new workspace (no Designer projects), clicked on Status View -> XML Schemas -> Import XSD. The new project wizard is display first since there are no projects (good). But if you cancel the new project wizard the import XSD wizard still is begin run even though there is no possibility of completing it. The XSD import wizard should not be run if the new project wizard is canceled. Should check to see if this issue occurs when running other wizards from the Status View. -- 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

13 years, 2 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1445) XML Relational File importer example is out of date

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1445: -------------------------------------- Summary: XML Relational File importer example is out of date Key: TEIIDDES-1445 URL: https://issues.jboss.org/browse/TEIIDDES-1445 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7, 7.6, 7.8 Reporter: Barry LaFond Assignee: Barry LaFond The example on page 1 of the XML Relational File importer has wrong tags in it that don't match schema. See attached for correct example. Also issue with indexes. The RelationalPrimaryKey.addColumn() method is resetting the parent to the PK. Line needs to be removed so parent of column remains the Table -- 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

13 years, 2 months

1
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2012