April 2012 - teiid-designer-issues

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

[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

11 years, 9 months

2
12
0 / 0

[JBoss JIRA] (TEIIDDES-1303) Create OData Importer

by Ted Jones (JIRA)

Ted Jones created TEIIDDES-1303: ----------------------------------- Summary: Create OData Importer Key: TEIIDDES-1303 URL: https://issues.jboss.org/browse/TEIIDDES-1303 Project: Teiid Designer Issue Type: Enhancement Components: Import/Export Affects Versions: 7.7 Reporter: Ted Jones Fix For: 7.7.1 To provide support for more complicated OData use cases, we should extend the XML Importer to create an OData importer. This importer will read the metadata of the service in the selected CP and determine what columns are allowable for input. We would then need to create an access pattern on the generated base table for these fields. These fields would be added to the URL of the service.. so the above Bank service URL would become: http://gw.esworkplace.sap.com/sap/opu/sdata/sap/DEMO_BANK/z_demo_bankColl... and the generated transformation should take the column values from the access pattern and build the URL accordingly in the invokeHttp() call. -- 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, 9 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1336) Consider removal of WS-Security option as unnecessary

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1336: ----------------------------------------- Summary: Consider removal of WS-Security option as unnecessary Key: TEIIDDES-1336 URL: https://issues.jboss.org/browse/TEIIDDES-1336 Project: Teiid Designer Issue Type: Sub-task Reporter: Paul Richardson Assignee: Paul Richardson Priority: Minor The security options for authenticated WSDLs are provided as BASIC and WS-Security. The latter is not considered necessary and should probably be removed from all situations, including the REST importer. -- 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, 9 months

2
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-1025) Fix Teiid Designer's Javadoc errors

by Barry LaFond (JIRA)

Fix Teiid Designer's Javadoc errors ----------------------------------- Key: TEIIDDES-1025 URL: https://issues.jboss.org/browse/TEIIDDES-1025 Project: Teiid Designer Issue Type: Bug Components: Housekeeping Affects Versions: 8.0 Reporter: Barry LaFond Priority: Critical Fix For: 8.0 An upgrade to our build system for 7.5 release exposed a number of broken Javadoc {@link xxxx.xxx.xxx} entries. Enabling the Javadoc validation and rebuilding will find a few thousand errors/warnings. Some from copying/pasting over the years, others from refactoring by hand, etc... We should take some time to clean this up. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 9 months

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

11 years, 9 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

11 years, 9 months

2
4
0 / 0

[JBoss JIRA] (TEIIDDES-1100) Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file

by Van Halbert (Created) (JIRA)

Using Flat File Importer, it doesn't recognize "\n" or "\r\n" in the file ------------------------------------------------------------------------- Key: TEIIDDES-1100 URL: https://issues.jboss.org/browse/TEIIDDES-1100 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.4.2 Reporter: Van Halbert Attachments: test.csv Trying to use the Import from Flat File option, but it doesn't recognize linefeeds of "\n" or "\r\n". -- 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, 9 months

4
7
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues April 2012