January 2010 - 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-231) Migrate Teiid Designer to use Eclipse 3.5 Target Platform

by Barry LaFond (JIRA)

Migrate Teiid Designer to use Eclipse 3.5 Target Platform --------------------------------------------------------- Key: TEIIDDES-231 URL: https://jira.jboss.org/jira/browse/TEIIDDES-231 Project: Teiid Designer Issue Type: Task Components: Eclipse Integration Affects Versions: 6.3 Reporter: Barry LaFond Assignee: Barry LaFond Fix For: 6.3 Upgraded Teiid Designer target platform to use Eclpse 3.5. This includes a new UML2 version that is incompatible with previous versions. Also included will be the Data Tools Platform so follow-on work for 6.4 release can be investigated. -- 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

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-248) WSDL to Relational Model Importer fails to import WSDLs that import other WSDLs correctly.

by John Doyle (JIRA)

WSDL to Relational Model Importer fails to import WSDLs that import other WSDLs correctly. ------------------------------------------------------------------------------------------ Key: TEIIDDES-248 URL: https://jira.jboss.org/jira/browse/TEIIDDES-248 Project: Teiid Designer Issue Type: Bug Affects Versions: 6.0.0, 6.1.0 Reporter: John Doyle Assignee: John Doyle Duplicates https://jira.jboss.org/jira/browse/JBEDSP-1140 -- 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

1
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-249) WSDL to Relational Model Importer fails to import WSDLs containing namespaces with xmlns in the namespace uri.

by John Doyle (JIRA)

WSDL to Relational Model Importer fails to import WSDLs containing namespaces with xmlns in the namespace uri. -------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-249 URL: https://jira.jboss.org/jira/browse/TEIIDDES-249 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0 Reporter: John Doyle Assignee: John Doyle Duplicates https://jira.jboss.org/jira/browse/JBEDSP-1141 -- 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

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-251) Designer's use of ResourceLocator class and URI's, performance problems exist with Eclipse 3.5

by Barry LaFond (JIRA)

Designer's use of ResourceLocator class and URI's, performance problems exist with Eclipse 3.5 ---------------------------------------------------------------------------------------------- Key: TEIIDDES-251 URL: https://jira.jboss.org/jira/browse/TEIIDDES-251 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 6.3 Reporter: Barry LaFond Assignee: Dan Florian Priority: Blocker Fix For: 6.3 Apparently Teiid Designer's use of Debugger preferences, it was discovered that our assumption that all plugins are folder-based (not jars) is resulting in major performance issues (UI) with 3.5 Eclipse. (Dan, can you fill in the blanks here???) -- 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, 4 months

2
2
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, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (TEIIDDES-253) Exception is produced when a binding property is set to its default value.

by John Doyle (JIRA)

Exception is produced when a binding property is set to its default value. -------------------------------------------------------------------------- Key: TEIIDDES-253 URL: https://jira.jboss.org/jira/browse/TEIIDDES-253 Project: Teiid Designer Issue Type: Bug Components: Teiid Integration Affects Versions: 6.2.0 Reporter: John Doyle Assignee: John Doyle Fix For: 6.3 This problem is shown when creating a Web Service as Relational Model with a style of Document - Literal. This is the default property value. java.lang.Exception: The value "Document - Literal" is not valid for property "EncodingStyle." -- 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, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-252) UML2 Class Loading Problem

by Dan Florian (JIRA)

UML2 Class Loading Problem -------------------------- Key: TEIIDDES-252 URL: https://jira.jboss.org/jira/browse/TEIIDDES-252 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 6.3 Environment: Ubuntu 9.04, Mac Snow Leopard Reporter: Dan Florian Priority: Blocker Fix For: 6.3 After creating a UML model I noticed that I could not create child objects in the model. There was nothing in the Message Log but looking in the workspace log I found this: !ENTRY org.teiid.designer.core 4 0 2010-01-14 11:17:13.220 !MESSAGE Unable to load class org.eclipse.uml2.Model using bundle org.teiid.designer.metamodels.uml2_6.3.0 [250] !ENTRY org.teiid.designer.core 4 0 2010-01-14 11:17:13.232 !MESSAGE Unable to load class org.eclipse.uml2.Package using bundle org.teiid.designer.metamodels.uml2_6.3.0 [250] -- 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, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (TEIIDDES-246) NULL ResourceSet assertion during Create Web Service model creation

by Barry LaFond (JIRA)

NULL ResourceSet assertion during Create Web Service model creation ------------------------------------------------------------------- Key: TEIIDDES-246 URL: https://jira.jboss.org/jira/browse/TEIIDDES-246 Project: Teiid Designer Issue Type: Bug Components: Eclipse Integration Affects Versions: 6.3 Reporter: Barry LaFond Assignee: Johnny Verhaeg Fix For: 6.3 Attachments: TEIIDDES_246_log.txt Launch 6.3 Designer (3.5 Eclipse platform based) 1) Create Project 2) Create Empty WS model by hand via New > Metadata Model wizard 3) Empty WS model is created, no errors Close & re-launch Designer 1) Create Project 2) Create Relational model with at least 1 table and columns (import will work too) 3) Select rel model and right-click select "Modeling > Create Web Service" action 4) Receive attached error 5) Create Empty WS model by hand via New > Metadata Model wizard 6) Receive "ResourceSet reference may not be null" error dialog. -- 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, 4 months

2
3
0 / 0

[JBoss JIRA] Closed: (TEIIDDES-185) Errors opening with Model Editor in Eclipse 3.5 M7 on Mac OS X

by Johnny Verhaeg (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-185?page=com.atlassian.jira.p... ] Johnny Verhaeg closed TEIIDDES-185. ----------------------------------- Resolution: Done Designer is now supported on Mac OSX 10.6 (Snow Leopard). > Errors opening with Model Editor in Eclipse 3.5 M7 on Mac OS X > -------------------------------------------------------------- > > Key: TEIIDDES-185 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-185 > Project: Teiid Designer > Issue Type: Bug > Components: Eclipse Integration > Affects Versions: 6.0.0 > Environment: eclipse.buildId=I20090430-2300 > java.version=1.6.0_07 > java.vendor=Apple Inc. > BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US > Framework arguments: -keyring /Users/btruitt/.eclipse_keyring -showlocation > Command-line arguments: -os macosx -ws cocoa -arch x86_64 -keyring /Users/btruitt/.eclipse_keyring -showlocation > teiid_designer_6.0.0.v20090427_SNAPSHOT > Reporter: Ben Truitt > Assignee: Johnny Verhaeg > Fix For: 6.3 > > Attachments: stack_trace_1.rtf, stack_trace_2.rtf, stack_trace_3.rtf, stack_trace_4.rtf, stack_trace_5.rtf, stack_trace_6.rtf, stack_trace_7.rtf, stack_trace_8.rtf, stack_trace_9.rtf > > > Hi - > Running on Eclipse 3.5 M7 with teiid_designer_6.0.0.v20090427_SNAPSHOT on mac os x java 1.6 64 bit, I am experiencing a couple of errors when I open an "xmi" model file by right-clicking in the model explorer view and choosing "open with", "model editor." > I get two separate error dialog boxes, then the Diagram editor appears with a blank canvas and no buttons in the left-side of the pane. > The error messages are: > Quote: > Error attempting to load a Model Object Editor Page plugin > ID = com.metamatrix.modeler.webservice.ui.editor.OperationObjectEditorPage > Quote: > Error attempting to load a Model Object Editor Page plugin > ID = com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage > I am using the most recent SNAPSHOT version of the Designer on Eclipse Version: 3.5.0 M7 (Build id: I20090430-2300), java.runtime.version=1.6.0_07-b06-153, on mac os x version 10.5.6. > In addition to the above error messages, I see the following errors logged in the Eclipse Error View (they appear in this chronological order): > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" > Error attempting to load a Model Object Editor Page plugin > ID = com.metamatrix.modeler.webservice.ui.editor.OperationObjectEditorPage > Error attempting to load a Model Object Editor Page plugin > ID = com.metamatrix.modeler.transformation.ui.editors.TransformationObjectEditorPage > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.connectorBindingLabelProvider" > Unable to load the Extended Model Label Provider "org.teiid.designer.dqp.ui.udfModelJarsLabelProvider" > Unhandled event loop exception > I will attach stack traces for each of these exceptions to the Jira issue. > -Ben Truitt -- 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, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues January 2010