June 2012 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-963) Add jboss tools runtime detector for Teid Servers

by Max Rydahl Andersen (JIRA)

Add jboss tools runtime detector for Teid Servers ------------------------------------------------- Key: TEIIDDES-963 URL: https://issues.jboss.org/browse/TEIIDDES-963 Project: Teiid Designer Issue Type: Bug Reporter: Max Rydahl Andersen Priority: Critical Add teid runtime detection so users don't have to setup teiid servers when already installed into EAP. extension point is: org.jboss.tools.runtime.core.runtimeDetectors -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

6
16
0 / 0

[JBoss JIRA] Created: (TEIIDDES-220) New Model Wizard prefs for XML Doc Model not getting picked up.

by Mark Drilling (JIRA)

New Model Wizard prefs for XML Doc Model not getting picked up. --------------------------------------------------------------- Key: TEIIDDES-220 URL: https://jira.jboss.org/jira/browse/TEIIDDES-220 Project: Teiid Designer Issue Type: Bug Components: Dialogs Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Mark Drilling Priority: Minor The mapping class generation preference is being saved, but is not being picked up correctly on relaunch of the New Model wizard. This results in the xml doc model potentially being generated with the incorrect mapping class generator preference. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 7 months

2
13
0 / 0

[JBoss JIRA] (TEIIDDES-1222) Convert Function Metamodel to built-in relational model MED

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1222: -------------------------------------- Summary: Convert Function Metamodel to built-in relational model MED Key: TEIIDDES-1222 URL: https://issues.jboss.org/browse/TEIIDDES-1222 Project: Teiid Designer Issue Type: Sub-task Reporter: Barry LaFond In order to retire the Function metamodel we need to replace it with extension properties on the relational metamodel via the new MED framework. in 7.5/7.6 the "Source Function" property (deterministic) is the only current built-in "relational" extended property. Probably could convert to use only 1 built-in MED that extends "Relational" metamodel. -- 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

11 years, 8 months

2
5
0 / 0

[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

11 years, 8 months

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

11 years, 8 months

3
6
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

11 years, 8 months

2
2
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

11 years, 8 months

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

11 years, 8 months

2
3
0 / 0

[JBoss JIRA] (TEIIDDES-1414) Remove Designer Preference: "Import Logical ER Models as View Relational Models"

by Mark Drilling (JIRA)

Mark Drilling created TEIIDDES-1414: --------------------------------------- Summary: Remove Designer Preference: "Import Logical ER Models as View Relational Models" Key: TEIIDDES-1414 URL: https://issues.jboss.org/browse/TEIIDDES-1414 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7 Reporter: Mark Drilling Fix For: 8.0 The "Import Logical ER Models as View Relational Models" preference is obsolete - we don't directly import ER models anymore. I believe this preference should be removed. -- 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

11 years, 8 months

2
2
0 / 0

[JBoss JIRA] (TEIIDDES-1311) Update Teiid Designer to reflect changes in server interface philosophy

by Barry LaFond (JIRA)

Barry LaFond created TEIIDDES-1311: -------------------------------------- Summary: Update Teiid Designer to reflect changes in server interface philosophy Key: TEIIDDES-1311 URL: https://issues.jboss.org/browse/TEIIDDES-1311 Project: Teiid Designer Issue Type: Task Affects Versions: 8.0 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 8.0 Changes to Teiid 8.0 and the underlying Application Server may have changed enough to warrent how Teiid Designer exposes it's Teiid server functions. This task is an umbrella for any sub-tasks required to upgrade Teiid Designer -- 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

11 years, 8 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues June 2012