[JBoss JIRA] (TEIIDDES-1884) Enhanced support for the native query procedure
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1884?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1884:
-----------------------------------
Fix Version/s: 8.5
> Enhanced support for the native query procedure
> -----------------------------------------------
>
> Key: TEIIDDES-1884
> URL: https://issues.jboss.org/browse/TEIIDDES-1884
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Fix For: 8.5
>
>
> Teiid translators can expose a procedure to execute arbitrary source queries. When operating with a dynamic vdb the appropriate metadata is automatically made available to the engine, but in Designer the user must manually add a procedure definition. For many users this is a difficult process - see the forum link.
> The complications here are that the procedure is selectively enabled and is allowed to have different names based upon the translator properties.
> The general procedure form is:
> create foreign procedure native (query in string, params in object varidaic) returns table(row_value object)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2017:
-----------------------------------
Fix Version/s: 8.4
> NPE while using Teiid Connection Importer
> -----------------------------------------
>
> Key: TEIIDDES-2017
> URL: https://issues.jboss.org/browse/TEIIDDES-2017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Fix For: 8.4
>
>
> While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2017) NPE while using Teiid Connection Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2017?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2017:
--------------------------------------
Assignee: Barry LaFond
> NPE while using Teiid Connection Importer
> -----------------------------------------
>
> Key: TEIIDDES-2017
> URL: https://issues.jboss.org/browse/TEIIDDES-2017
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> While trying to use "Teiid Connection >> Source Model" importer with new SOLR source type I encountered
> {code}
> java.lang.NullPointerException
> at org.teiid.designer.teiidimporter.ui.wizard.ShowDDLPage.setVisible(ShowDDLPage.java:201)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1259)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1238)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1227)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1225)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:915)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:428)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:628)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:826)
> at org.eclipse.jface.window.Window.open(Window.java:802)
> at org.eclipse.ui.internal.handlers.WizardHandler$Import.executeHandler(WizardHandler.java:152)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:279)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:290)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor49.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:224)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:167)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:213)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:420)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157)
> 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$5.handleEvent(ActionContributionItem.java:411)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> 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:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
> The dialog did not pop any dialog box about error, nor it can proceed any further, so notification given to user other than he/she can cancel it. But the above is logged in the "errors" panel.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2018:
--------------------------------------
Assignee: Barry LaFond
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Assignee: Barry LaFond
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2018) DDL importer creates wrong data type for "integer"
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2018?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2018:
-----------------------------------
Fix Version/s: 8.4
> DDL importer creates wrong data type for "integer"
> --------------------------------------------------
>
> Key: TEIIDDES-2018
> URL: https://issues.jboss.org/browse/TEIIDDES-2018
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.3
> Reporter: Ramesh Reddy
> Fix For: 8.4
>
>
> When using the Teiid Designer's "DDL importer" or "Teiid Connection >> Source Model",
> * if the DDL supplied is "Teiid" dialect
> * if the data type supplied is "integer"
> Then the resulting data type of the column/parameter is mapped "xs:decimal" which is aliased as "integer", which results in "big integer" at run time.
> This should be mapped to "xs:long" which is aliased as "int". The confusing thing is there is also "xs:integer" which is aliased to "long"
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2028:
----------------------------------------
Debugging shows:
While saveElementID() for: org.teiid.designer.metamodels.transformation.impl.MappingClassColumnImpl@110fbbf2 (name: outcome)
Then saveIDRefSingle() for: org.eclipse.emf.ecore.impl.EReferenceImpl@2b0f1190 (name: type) (ordered: true, unique: true, lowerBound: 1, upperBound: 1) (changeable: true, volatile: false, transient: false, defaultValueLiteral: null, unsettable: false, derived: false) (containment: false, resolveProxies: true)
{code}
XmlSaveImpl.saveIDRefSingle(EObject o, EStructuralFeature f)
{
EObject value = (EObject)helper.getValue(o, f);
{code}
The "value" returned here is of type *org.eclipse.xsd.impl.XSDSimpleTypeDefinitionImpl* where the "element" value is *null* which is probably the reason for the NPE.
Full object toString() is:
org.eclipse.xsd.impl.XSDSimpleTypeDefinitionImpl@1ffc159e (element: null) (name: SearchResults, targetNamespace: java:i3.intel.search.wsdl) (variety: atomic, final: null, lexicalFinal: null, validFacets: null)
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.4
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2028) Teiid tooling fails to create metamodel for web service
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2028?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2028:
----------------------------------------
Stack trace:
{code}
Script started on Wed 22 Jan 2014 03:33:53 PM EST
]0;rlucente@fedora-rlucente:~[?1034h[rlucente@fedora-rlucente ~]$ ~/jbdevstudio/jbdevstudio
Jan 22, 2014 3:34:50 PM org.modeshape.common.logging.LogFactory <clinit>
INFO: No custom logger, SLF4J implementation or Log4j located in the classpath. ModeShape will use the JDK logger for logging.
Exception in thread "ModelBuffer.Save" java.lang.NullPointerException
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getURIFragment(XMLHelperImpl.java:713)
at org.eclipse.emf.ecore.xmi.impl.XMLHelperImpl.getIDREF(XMLHelperImpl.java:747)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveIDRefSingle(XMLSaveImpl.java:1987)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:299)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1328)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1219)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1176)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1037)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2412)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1548)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1219)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1176)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1037)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2412)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1548)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1219)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1176)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1037)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2412)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1548)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1219)
at org.teiid.designer.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:249)
at org.eclipse.emf.ecore.xmi.impl.XMISaveImpl.writeTopObjects(XMISaveImpl.java:84)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.traverse(XMLSaveImpl.java:590)
at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.save(XMLSaveImpl.java:251)
at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doSave(XMLResourceImpl.java:365)
at org.teiid.designer.core.resource.xmi.MtkXmiResourceImpl.doSave(MtkXmiResourceImpl.java:356)
at org.eclipse.emf.ecore.resource.impl.ResourceImpl.save(ResourceImpl.java:1430)
at org.teiid.designer.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:567)
at org.teiid.designer.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:496)
{code}
> Teiid tooling fails to create metamodel for web service
> -------------------------------------------------------
>
> Key: TEIIDDES-2028
> URL: https://issues.jboss.org/browse/TEIIDDES-2028
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 8.3
> Reporter: Van Halbert
> Assignee: Ted Jones
> Fix For: 8.4
>
>
> Description of problem:
> Unable to build metamodel for customer provided WSDL file. Simplified the web service to a single operation that uses three embedded schemas under wsdl types. Stack trace from NPE appears in console log and errors occur after wizard is executed. Screenshots for wizard, wsdl file, and stack trace are attached.
> I'm able to validate the WSDL and I can generate a web service from the WSDL within a dynamic web project using the web service wizard.
> Version-Release number of selected component (if applicable):
> JBDS 7.1, latest Teiid tooling from https://devstudio.jboss.com/updates/7.0-development/integration-stack/, DV 6.0.0.CR2
> How reproducible:
> Everytime
> Steps to Reproduce:
> 1. Create Teiid Model Project
> 2. Import WSDL under schemas folder
> 3. Use Teiid Metamodel wizard to consume WSDL
> see BZ for attachments.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months
[JBoss JIRA] (TEIIDDES-2030) Querying webservice of VDB throws javax.naming.NameNotFoundException
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2030?page=com.atlassian.jira.plu... ]
RH Bugzilla Integration commented on TEIIDDES-2030:
---------------------------------------------------
Lucie Fabrikova <lfabriko(a)redhat.com> changed the Status of [bug 1057076|https://bugzilla.redhat.com/show_bug.cgi?id=1057076] from NEW to VERIFIED
> Querying webservice of VDB throws javax.naming.NameNotFoundException
> --------------------------------------------------------------------
>
> Key: TEIIDDES-2030
> URL: https://issues.jboss.org/browse/TEIIDDES-2030
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.3.1
> Environment: JBTIS 4.1.3.Final, JBDS 7.1.0.GA, DV 6 CR2, Fedora 19, Java oracle jdk 1.7.0_45, teiid translator 8.4 (https://repository.jboss.org/nexus/content/repositories/public-jboss/org/...)
> Reporter: Lucie Fabrikova
> Attachments: ConsumeWSNoJNDI.zip, countryInfoNoJNDI.vdb, countryInfoNoJNDI.war
>
>
> Querying (via soapui) a webservice created from VDB which contains a model without a JNDI name (model MarketData with yahoo translator, viz TDES-2024), server throws exception javax.naming.NameNotFoundException.
> If the model without JNDI is removed from VDB, the query is successful.
> (the models in project were created via "Consume a SOAP web service" cheat sheet from DV6 doc., detailed instructions in TestSpecs/Designer8-updatedE2eConsumeSoapWS-cheatSheetCompletion.odt)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 4 months