September 2009 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-192) Unable to create vdb in Windows environment - Missing model import to resource......builtInDataTypes.xsd

by Warren Gibson (JIRA)

Unable to create vdb in Windows environment - Missing model import to resource......builtInDataTypes.xsd -------------------------------------------------------------------------------------------------------- Key: TEIIDDES-192 URL: https://jira.jboss.org/jira/browse/TEIIDDES-192 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 6.0.0 Environment: Teiid Designer in Windows environment Reporter: Warren Gibson Attachments: Modelmissingimport.zip I was creating a new set of BQT vdbs. BQT Models in workspace were all error free. Created a vdb and when models were added to vdb the following error occurred. The vdb is not usable. Missing model import to resource../../../Documents%2520and%2520Settings/admin.SLNTQM13/workspace5-18/. metadata/.plugins/org.teiid.designer.vdb.edit/vdbWorkingForlder/1242654827171_57514671701635058-/builtInDataTypes.xsd This same set of models were used to create a vdb in Linux successfully. Project is attached. -- 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

14 years, 3 months

4
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-230) Error while adding a "Web Service" model to the VDB

by Ramesh Reddy (JIRA)

Error while adding a "Web Service" model to the VDB --------------------------------------------------- Key: TEIIDDES-230 URL: https://jira.jboss.org/jira/browse/TEIIDDES-230 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.2.0 Reporter: Ramesh Reddy 1) I have used "Web Service as Relational Source Model" import and created a model from URL "http://ws.fraudlabs.com/zipcodeworldUS_webservice.asmx?wsdl" 2) Created VDB and tried to add the created model to the VDB, and met with below exception java.lang.NullPointerException at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:719) at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:753) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1954) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1300) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248) at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:90) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:592) at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:256) at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:206) at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:354) at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1406) at com.metamatrix.vdb.internal.edit.VdbEditingContextImpl.addToTempDirectory(VdbEditingContextImpl.java:4875) at com.metamatrix.vdb.internal.edit.VdbEditingContextImpl.save(VdbEditingContextImpl.java:1122) at com.metamatrix.vdb.internal.edit.VdbEditingContextImpl.save(VdbEditingContextImpl.java:660) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor$1.execute(VdbEditor.java:315) at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:106) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1800) at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:118) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.saveAll(VdbEditor.java:364) at com.metamatrix.modeler.internal.vdb.ui.editor.VdbEditor.doSave(VdbEditor.java:286) at org.eclipse.ui.internal.SaveableHelper$2.run(SaveableHelper.java:151) at org.eclipse.ui.internal.SaveableHelper$5.run(SaveableHelper.java:274) at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464) at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372) at org.eclipse.jface.window.ApplicationWindow$1.run(ApplicationWindow.java:759) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.window.ApplicationWindow.run(ApplicationWindow.java:756) at org.eclipse.ui.internal.WorkbenchWindow.run(WorkbenchWindow.java:2578) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:282) at org.eclipse.ui.internal.SaveableHelper.runProgressMonitorOperation(SaveableHelper.java:261) at org.eclipse.ui.internal.SaveableHelper.savePart(SaveableHelper.java:156) at org.eclipse.ui.internal.EditorManager.savePart(EditorManager.java:1357) at org.eclipse.ui.internal.WorkbenchPage.savePart(WorkbenchPage.java:3328) at org.eclipse.ui.internal.WorkbenchPage.saveEditor(WorkbenchPage.java:3341) at org.eclipse.ui.internal.SaveAction.run(SaveAction.java:76) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) at org.eclipse.jface.action.ActionContributionItem$6.handleEvent(ActionContributionItem.java:452) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1176) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3493) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3112) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2369) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2221) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194) 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:368) 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:559) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514) at org.eclipse.equinox.launcher.Main.run(Main.java:1311) -- 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

14 years, 3 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-213) Update Designer To Use Teiid Embedded 6.2.0

by Barry LaFond (JIRA)

Update Designer To Use Teiid Embedded 6.2.0 ------------------------------------------- Key: TEIIDDES-213 URL: https://jira.jboss.org/jira/browse/TEIIDDES-213 Project: Teiid Designer Issue Type: Task Components: Teiid Integration Affects Versions: 6.2.0 Reporter: Barry LaFond Assignee: Johnny Verhaeg Priority: Blocker Fix For: 6.2.0 Upgrade Teiid Designer to use Teiid Embedded 6.2 code-base. This includes forking applicable query/metadata common code -- 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

14 years, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-221) Add internationalization support in Designer

by Debbie Steigner (JIRA)

Add internationalization support in Designer -------------------------------------------- Key: TEIIDDES-221 URL: https://jira.jboss.org/jira/browse/TEIIDDES-221 Project: Teiid Designer Issue Type: Feature Request Components: Data Preview, Editors Reporter: Debbie Steigner Fix For: 6.1.0 Current Designer doesn't display international characters (Chinese, Japanese, etc.) Please add this to future release. -- 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

14 years, 7 months

2
1
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-61) Fix failing WSDL-Relational SOAP Array tests.

by John Doyle (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-61?page=com.atlassian.jira.pl... ] John Doyle updated TEIIDDES-61: ------------------------------- Fix Version/s: Future (was: 6.2.0) > Fix failing WSDL-Relational SOAP Array tests. > --------------------------------------------- > > Key: TEIIDDES-61 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-61 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 6.0.0 > Reporter: John Doyle > Assignee: John Doyle > Fix For: Future > > Attachments: FailingTests.zip > > > The attached tests were not maintained because the folders were not marked as src folders. They do not pass now but are important tests that need to be figured out and made to pass. -- 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

14 years, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-225) Add Derby XA Connector Type to Designer

by Ted Jones (JIRA)

Add Derby XA Connector Type to Designer --------------------------------------- Key: TEIIDDES-225 URL: https://jira.jboss.org/jira/browse/TEIIDDES-225 Project: Teiid Designer Issue Type: Feature Request Affects Versions: 6.2.0 Reporter: Ted Jones In order to support an updateable Portfolio database for our Teiid example, we need to be able to create a Derby XA connector. This connector type need to be added to the list of our pre-defined connectors. -- 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

14 years, 8 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues September 2009