July 2012 - teiid-designer-issues

[JBoss JIRA] (TEIIDDES-1451) Change Nightly build job to use git rather than svn

by Paul Richardson (JIRA)

Paul Richardson created TEIIDDES-1451: ----------------------------------------- Summary: Change Nightly build job to use git rather than svn Key: TEIIDDES-1451 URL: https://issues.jboss.org/browse/TEIIDDES-1451 Project: Teiid Designer Issue Type: Task Affects Versions: 8.0 Reporter: Paul Richardson Fix For: 8.0 The nightly build points to the 7.7.x release branch https://hudson.qa.jboss.com/hudson/view/SOA-Team/view/SOATools-3.3.0/job/... Given this release branch is being maintained in svn until the release of 8.0, the nightly build will continue to point to svn. Only on the release of 8.0, should this be reconfigured. -- 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, 3 months

2
1
0 / 0

[JBoss JIRA] (TEIIDDES-1453) Help for Web Service project example has odd character set and older screenshots

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1453: ------------------------------------- Summary: Help for Web Service project example has odd character set and older screenshots Key: TEIIDDES-1453 URL: https://issues.jboss.org/browse/TEIIDDES-1453 Project: Teiid Designer Issue Type: Bug Components: Documentation Affects Versions: 7.7.1 Environment: Fedora 16 Reporter: Paul Nittel The HTML help for the Web services demo displays off characters and has some out-of-date screenshots. See the attached for examples. -- 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, 3 months

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

13 years, 3 months

4
7
0 / 0

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1010: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a comment on [bug 780725|https://bugzilla.redhat.com/show_bug.cgi?id=780725] > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1010) Indexes are not qualified when imported with Teiid Designer

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1010?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1010: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780725|https://bugzilla.redhat.com/show_bug.cgi?id=780725] from ASSIGNED to CLOSED > Indexes are not qualified when imported with Teiid Designer > ----------------------------------------------------------- > > Key: TEIIDDES-1010 > URL: https://issues.jboss.org/browse/TEIIDDES-1010 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.4 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.0 > > > Having multiple indexes with the same name (for example, 'PrimaryKey') imported results in a conflict or merging of the indexes. This generates messages complaining of an index referring to multiple tables in the Teiid Designer perspective. The indexes should be qualified in order to remain unique or generated as a child of the associated table in order to avoid these messages. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1009: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> changed the Status of [bug 780722|https://bugzilla.redhat.com/show_bug.cgi?id=780722] from NEW to CLOSED > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > Fix For: 8.0 > > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1009: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a comment on [bug 780723|https://bugzilla.redhat.com/show_bug.cgi?id=780723] > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > Fix For: 8.0 > > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1009) Improve Designer "Metadata from Text files on file system" import option

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1009?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1009: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com> made a comment on [bug 780722|https://bugzilla.redhat.com/show_bug.cgi?id=780722] > Improve Designer "Metadata from Text files on file system" import option > ------------------------------------------------------------------------ > > Key: TEIIDDES-1009 > URL: https://issues.jboss.org/browse/TEIIDDES-1009 > Project: Teiid Designer > Issue Type: Feature Request > Components: Import/Export > Affects Versions: 7.4 > Reporter: Debbie Steigner > Assignee: Barry LaFond > Labels: eds > Fix For: 8.0 > > > Currently, this importer is very limited on the data that can be imported. i.e. on columns you can only import: Name, Datatype, Length and Description. All the Model, Table and Column properties should be available to import. Nullability, Cardinality, Precision, Comments, etc. > Also, change name to "Metadata from Flat or Text File" to distinguish it from "Metadata from Teiid Metadata File" -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1364) Validating WSDL imported from Amazon.com fails with NPE

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1364: ------------------------------------- Summary: Validating WSDL imported from Amazon.com fails with NPE Key: TEIIDDES-1364 URL: https://issues.jboss.org/browse/TEIIDDES-1364 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 7.7.1 Environment: JBDS 5.0 Beta 3 with SOAtooling Reporter: Paul Nittel When I imported WSDL from http://webservices.amazon.com/AWSECommerceService/AWSECommerceService.wsdl I received a null pointer exception on the validation page of the WSDL to Web service model wizard. There was no entry in the Designer's log file. A screenshot of the error is attached. -- 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, 3 months

3
13
0 / 0

[JBoss JIRA] (TEIIDDES-1443) Procedural-Relational Mapping test fails with IllegalArgumentException

by Paul Nittel (JIRA)

Paul Nittel created TEIIDDES-1443: ------------------------------------- Summary: Procedural-Relational Mapping test fails with IllegalArgumentException Key: TEIIDDES-1443 URL: https://issues.jboss.org/browse/TEIIDDES-1443 Project: Teiid Designer Issue Type: Bug Components: Modeling Environment: JBDS 5.0 with SOA-tooling CR2 Reporter: Paul Nittel Description of problem: Adding a procedure as a source to a transformation resulted in an IllegalArgumentException Version-Release number of selected component (if applicable): JBDS 5.0 with SOA-tooling CR2 How reproducible: Seems highly reproducible Steps to Reproduce: 1. Import metadata 2. Create a procedure 3. Create a view relational mmodel with a base table 4. Add the procedure as a source to the transformation (SELECT * FROM procedure) 5. Validate the transformation SQL Actual results: eclipse.buildId=unknown java.version=1.6.0_31 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US Framework arguments: -product com.jboss.jbds.product.product Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.jboss.jbds.product.product Error Wed Jul 11 10:17:05 CDT 2012 Error encountered while validating the transformation. java.lang.IllegalArgumentException: Expected argument to be an instance of com.metamatrix.modeler.core.metadata.runtime.TableRecord; was instance of org.teiid.query.metadata.TempMetadataID at org.teiid.core.util.ArgCheck.isInstanceOf(ArgCheck.java:354) at org.teiid.core.util.ArgCheck.isInstanceOf(ArgCheck.java:338) at com.metamatrix.modeler.transformation.metadata.TransformationMetadata.getUniqueKeysInGroup(TransformationMetadata.java:802) at org.teiid.query.resolver.util.ResolverUtil.findKeyPreserved(ResolverUtil.java:1016) at org.teiid.query.resolver.util.ResolverUtil.findKeyPreserved(ResolverUtil.java:951) at org.teiid.query.validator.UpdateValidator.internalValidate(UpdateValidator.java:437) at org.teiid.query.validator.UpdateValidator.validate(UpdateValidator.java:344) at com.metamatrix.modeler.transformation.validation.TransformationValidator.validateCommand(TransformationValidator.java:550) at com.metamatrix.modeler.transformation.validation.TransformationValidator.validateSql(TransformationValidator.java:351) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.createStatus(SqlMappingRootCache.java:721) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.getStatus(SqlMappingRootCache.java:802) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.getStatus(SqlMappingRootCache.java:763) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.getSqlString(SqlMappingRootCache.java:657) at com.metamatrix.modeler.internal.transformation.util.TransformationHelper.getSqlString(TransformationHelper.java:402) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.setEditorContent(TransformationObjectEditorPage.java:951) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.handleTransformationStatusChangeEvent(TransformationObjectEditorPage.java:1617) at com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage.processEvent(TransformationObjectEditorPage.java:2623) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.notifyEventListeners(SqlMappingRootCache.java:945) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.invalidateStatus(SqlMappingRootCache.java:488) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.invalidateSelectStatus(SqlMappingRootCache.java:84) at com.metamatrix.modeler.internal.transformation.util.SqlMappingRootCache.invalidateSelectStatus(SqlMappingRootCache.java:76) at com.metamatrix.modeler.transformation.ui.util.TransformationNotificationListener.handleSqlAliasAddNotifications(TransformationNotificationListener.java:1019) at com.metamatrix.modeler.transformation.ui.util.TransformationNotificationListener.handleNotifications(TransformationNotificationListener.java:222) at com.metamatrix.modeler.transformation.ui.util.TransformationNotificationListener.notifyChanged(TransformationNotificationListener.java:173) at org.eclipse.emf.edit.provider.ChangeNotifier.fireNotifyChanged(ChangeNotifier.java:51) at com.metamatrix.modeler.internal.core.transaction.UnitOfWorkImpl.commit(UnitOfWorkImpl.java:251) at com.metamatrix.modeler.core.ModelerCore.commitTxn(ModelerCore.java:363) at com.metamatrix.modeler.transformation.ui.part.TransformationDropEditPartHelper.drop(TransformationDropEditPartHelper.java:67) at com.metamatrix.modeler.diagram.ui.part.AbstractDefaultEditPart.drop(AbstractDefaultEditPart.java:823) at com.metamatrix.modeler.diagram.ui.editor.DiagramDropTargetAdapter.drop(DiagramDropTargetAdapter.java:80) at org.eclipse.jface.util.DelegatingDropAdapter$3.run(DelegatingDropAdapter.java:211) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:49) at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:175) at org.eclipse.jface.util.DelegatingDropAdapter.drop(DelegatingDropAdapter.java:209) at org.eclipse.swt.dnd.DNDListener.handleEvent(DNDListener.java:90) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1062) at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:774) at org.eclipse.swt.dnd.DropTarget.Drop(DropTarget.java:456) at org.eclipse.swt.dnd.DropTarget.Drop_64(DropTarget.java:392) at org.eclipse.swt.dnd.DropTarget$3.method6(DropTarget.java:260) at org.eclipse.swt.internal.ole.win32.COMObject.callback6(COMObject.java:119) at org.eclipse.swt.internal.ole.win32.COM.DoDragDrop(Native Method) at org.eclipse.swt.dnd.DragSource.drag(DragSource.java:363) at org.eclipse.swt.dnd.DragSource.access$0(DragSource.java:289) at org.eclipse.swt.dnd.DragSource$1.handleEvent(DragSource.java:172) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4165) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3754) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) Expected results: No exception, just a relational base 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, 3 months

3
15
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues July 2012