January 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-216) Designer removes parentheses around criteria in ansi join when using compound ON

by Marc Shirley (JIRA)

Designer removes parentheses around criteria in ansi join when using compound ON -------------------------------------------------------------------------------- Key: TEIIDDES-216 URL: https://jira.jboss.org/jira/browse/TEIIDDES-216 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.1.0 Reporter: Marc Shirley In Designer, when validating a transformation that has compound criteria in an ansi join statement's ON, the parentheses are removed and the order of operations is modified as a result. This does not appear to occur when using the same parentheses structure in WHERE criteria. Before validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON (a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL OR a.INTNUM = 11) After validation: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON a.INTKEY = b.INTKEY AND (a.INTNUM IS NULL) OR (a.INTNUM = 11) After validating a second time: SELECT * FROM bqt.SMALLA AS a INNER JOIN bqt.SMALLB AS b ON ((a.INTKEY = b.INTKEY) AND (a.INTNUM IS NULL)) OR (a.INTNUM = 11) -- 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

12 years, 2 months

5
9
0 / 0

[JBoss JIRA] Created: (TEIIDDES-813) Fix Test Fragments That Are Calling Protected And Package Private Methods In Classes Found In Other Plugins

by Dan Florian (JIRA)

Fix Test Fragments That Are Calling Protected And Package Private Methods In Classes Found In Other Plugins ----------------------------------------------------------------------------------------------------------- Key: TEIIDDES-813 URL: https://issues.jboss.org/browse/TEIIDDES-813 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.2 Reporter: Dan Florian Fix For: Future The org.teiid.designer.jdbc.test and org.teiid.designer.jdbc.relational.test fragments are calling protected and package private methods in classes that our not found in their host plugins. This is not allowed in OSGi and their tests fail during the nightly build. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

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

12 years, 3 months

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

12 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-122) Add WSDL 2.0 Support to Designer for Data Services

by Ted Jones (JIRA)

Add WSDL 2.0 Support to Designer for Data Services -------------------------------------------------- Key: TEIIDDES-122 URL: https://jira.jboss.org/jira/browse/TEIIDDES-122 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 6.0.0 Reporter: Ted Jones Fix For: 6.0.0 In order to support REST (see TEIID-417), we need to allow for the generation of WSDL 2.0 specific WSDL. We still need to allow for the generation of WSDL 1.1 since WSDL 2.0 is not widely supported by many tools. There should be an option in the Designer to specify which version of the WSDL specification to use when generating the WSDL file. I suggest putting the option on the Web Services tab of the VDB, but I am open for other suggestions. Alternatively, we could add the WSDL using both specifications in separate WSDL files and then provide a different WSDL URL to get one or the other. This approach seems like overkill to me though and would have farther reaching ramifications. Ideally this would be completed for Westport. -- 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

12 years, 4 months

2
12
0 / 0

[JBoss JIRA] Created: (TEIIDDES-420) Add bundle version information to all plug-in dependencies

by John Verhaeg (JIRA)

Add bundle version information to all plug-in dependencies ---------------------------------------------------------- Key: TEIIDDES-420 URL: https://jira.jboss.org/jira/browse/TEIIDDES-420 Project: Teiid Designer Issue Type: Task Components: Housekeeping Affects Versions: 6.3 Reporter: John Verhaeg Fix For: 7.0 To ensure our we don't conflict with other plug-ins in JBT, JBDS, or any other plug-ins a client may have installed in Eclipse, we need to specify what versions of dependencies we are compatible with. -- 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

12 years, 5 months

3
10
0 / 0

[JBoss JIRA] Created: (TEIIDDES-152) Update the function model to support vararg functions

by Steven Hawkins (JIRA)

Update the function model to support vararg functions ----------------------------------------------------- Key: TEIIDDES-152 URL: https://jira.jboss.org/jira/browse/TEIIDDES-152 Project: Teiid Designer Issue Type: Feature Request Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins Vararg support allows for functions with any number of parameters. It requires adding additional metadata to a parameter or function to indicate that the last parameter accepts any number of arguments of that type. -- 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

12 years, 5 months

2
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-802) Tests Using PowerMock Fail When Running Tycho Build

by Dan Florian (JIRA)

Tests Using PowerMock Fail When Running Tycho Build --------------------------------------------------- Key: TEIIDDES-802 URL: https://issues.jboss.org/browse/TEIIDDES-802 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.1 Reporter: Dan Florian Fix For: Future The tests in the projects that use PowerMock are not being run during the nightly build. The following projects use PowerMock: 1. org.teiid.designer.core.test 2. org.teiid.designer.ddl.importer.test 3. org.teiid.designer.dqp.test 4. org.teiid.designer.vdb.test Once the problem is fixed, references to these projects need to be uncommented in the tests/pom.xml and in org.teiid.designer.tests.feature/feature.xml so that their tests will be run in the nightly build. I've investigated using the PowerMockRule instead of @RunWith( PowerMockRunner.class ) in the test. In the pom.xml, I've tried adding dependencies to PowerMock and also dependencies to the maven-osgi-test-plugin to PowerMock. Didn't have any luck with anything I've tried so far. In the root directory of one of the above projects execute the following command to run a local build and run tests of that one project: mvn3 clean install -B -fae -e -P helios-remote-target -X Here are some example pom.xml code that I have tried: <build> <plugin> <groupId>org.sonatype.tycho</groupId> <artifactId>maven-osgi-test-plugin</artifactId> <version>${tychoVersion}</version> <dependencies> <dependency> <groupId>org.jboss.tools</groupId> <artifactId>org.powermock.osgi</artifactId> <version>1.4.7</version> </dependency> </dependencies> </plugin> </build> -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
4
0 / 0

[JBoss JIRA] Created: (TEIIDDES-803) Fix Ignored Tests So That They Will Be Run

by Dan Florian (JIRA)

Fix Ignored Tests So That They Will Be Run ------------------------------------------ Key: TEIIDDES-803 URL: https://issues.jboss.org/browse/TEIIDDES-803 Project: Teiid Designer Issue Type: Task Components: Build Affects Versions: 7.2 Reporter: Dan Florian Fix For: Future These tests are intentionally not being run by the build and need to be fixed: 1. org.teiid.designer.core.test/TestModelEditor: has renamed tests so that those tests will not be run 2. org.teiid.designer.dqp.test/ServerTest: this test class has been commented out in pom.xml 3. org.teiid.designer.query.ui.test/TestDisplayNodeFactory: has renamed tests so that those tests will not be run 4. org.teiid.designer.transformation.test/TestPerformanceIndexFilePerRecordType: (a) has renamed tests so that those tests won't run, and (b) its helpCreateIndexFile() method is swallowing failed assertions and shouldn't 5. a search of // TODO comments should be done to find other ignored tests For tests in projects that use PowerMock, TEIIDDES-802 will need to be fixed first. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 5 months

3
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-402) Refactor Packages to replace com.metamatrix with org.teiid.xxx

by Barry LaFond (JIRA)

Refactor Packages to replace com.metamatrix with org.teiid.xxx -------------------------------------------------------------- Key: TEIIDDES-402 URL: https://jira.jboss.org/jira/browse/TEIIDDES-402 Project: Teiid Designer Issue Type: Sub-task Affects Versions: 7.0 Reporter: Barry LaFond Priority: Blocker Fix For: 7.0 Refactor Packages - Replace "metamatrix" with "teiid' - Revisit our package structuring to address inconsistent use of internal vs public packages -- 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

12 years, 5 months

1
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2011