[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ]
Paul Richardson commented on TEIIDDES-1570:
-------------------------------------------
Barry,
The commit correctly fixes the problem but would it not now be incorrect for a 7.7 runtime client. Consider there maybe 2 options:
a) Do a simple if statement on the version of the default teiid server as to whether include the extra parameter
b) More elegant but more work would be to add a method to the IQueryService to request the statement entirely. The default QueryService will return the appropriate statement for the default server
What do you think?
> Incorrect parameter types in invokeHttp
> ---------------------------------------
>
> Key: TEIIDDES-1570
> URL: https://issues.jboss.org/browse/TEIIDDES-1570
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.0
> Reporter: Daniel Susín
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: invokeHttp_parameters.jpg
>
>
> In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value.
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1164) CLONE - Index metadata should not treat cardinality 0 as unknown
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1164?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1164:
----------------------------------------
Relaxing the lower bounds to -1 the following is the output of the Table Word from RuntimeAdapter. Includes Cardinality of -1 and the IndexVersion of 10.
B PARTSSUPPLIER_COPY.TESTTABLEA mmuuid:55edaa2b-946c-486e-85cc-8d32af313cfd PartsSupplier_COPY.TestTableA -1 0 0010 /TEIIDDES-1164/PartsSupplier_COPY.xmi TestTableA ¡10
> CLONE - Index metadata should not treat cardinality 0 as unknown
> ----------------------------------------------------------------
>
> Key: TEIIDDES-1164
> URL: https://issues.jboss.org/browse/TEIIDDES-1164
> Project: Teiid Designer
> Issue Type: Quality Risk
> Components: Teiid Integration
> Affects Versions: 6.0.0
> Reporter: Steven Hawkins
> Assignee: Paul Richardson
> Fix For: 8.1
>
>
> The default cardinality is currently 0, which is treated as unknown, however it would be better if the default were something like -1 instead. This will require introducing a new index file version (so that older vdbs with a value of 0 can be understood as meaning unknown) and updating the teiid/designer metadata defaults for cardinality as -1.
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-704) NPE while constructing XML Documents from old/custom Parts XML Schema
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-704?page=com.atlassian.jira.plug... ]
Barry LaFond updated TEIIDDES-704:
----------------------------------
Fix Version/s: No Future
(was: 8.1)
There's something about the attached XSD file that's non standard and ending up with an NPE. Spent time in Debug with no progress. Tried fixing/changing Schema and no progress.
Since this was a home-grown XSD file, going to push to NO FUTURE and wait for legitimate external (more realistic) use case if it ever pops up
> NPE while constructing XML Documents from old/custom Parts XML Schema
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-704
> URL: https://issues.jboss.org/browse/TEIIDDES-704
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling
> Affects Versions: 7.1.1
> Reporter: Barry LaFond
> Assignee: Barry LaFond
> Fix For: No Future
>
>
> TEIIDDES-664 exposed a problem with displaying a error dialog when XML Document creation fails. This was fixed.
> What's not fixed is the NPE that is resulting from the schema involved.
> See attached Schema and create an XML Document from the PartOrder root element.
> Exception in thread "ModelBuffer.Save" 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:1972)
> at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveIDRefSingle(MtkXmiSaveImpl.java:298)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1318)
> at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533)
> at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533)
> at com.metamatrix.modeler.internal.core.resource.xmi.MtkXmiSaveImpl.saveElementID(MtkXmiSaveImpl.java:248)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1174)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveElement(XMLSaveImpl.java:1035)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveContainedMany(XMLSaveImpl.java:2386)
> at org.eclipse.emf.ecore.xmi.impl.XMLSaveImpl.saveFeatures(XMLSaveImpl.java:1533)
> 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.modeler.internal.core.workspace.ModelBufferImpl.saveInTransaction(ModelBufferImpl.java:559)
> at com.metamatrix.modeler.internal.core.workspace.ModelBufferImpl$1.run(ModelBufferImpl.java:488)
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1570.
------------------------------------
Resolution: Done
1) Swapped datatypes
2) Added 4th parameter for stream >>> 'TRUE' in generated SQL
> Incorrect parameter types in invokeHttp
> ---------------------------------------
>
> Key: TEIIDDES-1570
> URL: https://issues.jboss.org/browse/TEIIDDES-1570
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.0
> Reporter: Daniel Susín
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: invokeHttp_parameters.jpg
>
>
> In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value.
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1436) Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1436?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1436:
--------------------------------
Assignee: Barry LaFond (was: Ted Jones)
> Hand Generated XML Document Models do not Correctly Associate Namespace URI/Prefix with Elements
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1436
> URL: https://issues.jboss.org/browse/TEIIDDES-1436
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 7.7.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: foo.zip
>
>
> "Document models can be created that have nested namespaces, and Teiid contains code to use different namespace prefixes for nested elements. However at least for my simple test case (see attached) the generated mapping document does not contain any namespaceURI information for the elements - it only has the namespace declarations. It would appear that the logic in MappingDocumentFormatter is not correctly associating the prefix/uri with elements at least for a simple hand made document model. I don't know if things are different when starting with a schema." - SteveH
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1544) Error While Generating WAR in Teiid 8.0
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1544?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1544:
--------------------------------
Summary: Error While Generating WAR in Teiid 8.0 (was: Error While Genearting WAR in Teiid 8.0)
> Error While Generating WAR in Teiid 8.0
> ---------------------------------------
>
> Key: TEIIDDES-1544
> URL: https://issues.jboss.org/browse/TEIIDDES-1544
> Project: Teiid Designer
> Issue Type: Bug
> Components: Web Services Support
> Affects Versions: 8.0
> Reporter: Ajit Kumar Nayak
> Assignee: Ted Jones
> Fix For: 8.1
>
>
> Hi,
> I am using
> JBOSS AS 7.1.1
> teiid-8.0.0.Final-jboss-dist
> teiid-designer-8.0.0.Beta1-v20121114-1958-H144.zip
> jbossws-cxf-4.1.0.Final
> I am getting error while creating CXF-WAR for my VDB
> As
> java.lang.RuntimeException: File SimpleDatatypes-instance does not exist.
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.generateWsdl(DefaultWebArchiveBuilderImpl.java:718)
> at org.teiid.designer.runtime.ui.wizards.webservices.util.DefaultWebArchiveBuilderImpl.createWebArchive(DefaultWebArchiveBuilderImpl.java:236)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.execute(WarDeploymentInfoDialog.java:195)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog$1.run(WarDeploymentInfoDialog.java:150)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:464)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:372)
> at org.eclipse.jface.dialogs.ProgressMonitorDialog.run(ProgressMonitorDialog.java:507)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.okPressed(WarDeploymentInfoDialog.java:159)
> at org.eclipse.jface.dialogs.Dialog.buttonPressed(Dialog.java:472)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624)
> 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:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)
> at org.eclipse.jface.window.Window.open(Window.java:801)
> at org.teiid.designer.runtime.ui.wizards.webservices.WarDeploymentInfoDialog.open(WarDeploymentInfoDialog.java:171)
> at org.teiid.designer.runtime.ui.actions.GenerateWarAction.run(GenerateWarAction.java:116)
> 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$5.handleEvent(ActionContributionItem.java:411)
> 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:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1029)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:923)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:86)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:588)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:543)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> 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:353)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:180)
> 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:629)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:584)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1438)
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1570:
--------------------------------
Assignee: Barry LaFond (was: Ted Jones)
> Incorrect parameter types in invokeHttp
> ---------------------------------------
>
> Key: TEIIDDES-1570
> URL: https://issues.jboss.org/browse/TEIIDDES-1570
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.0
> Reporter: Daniel Susín
> Assignee: Barry LaFond
> Fix For: 8.1
>
> Attachments: invokeHttp_parameters.jpg
>
>
> In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value.
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1570) Incorrect parameter types in invokeHttp
by Ted Jones (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1570?page=com.atlassian.jira.plu... ]
Ted Jones updated TEIIDDES-1570:
--------------------------------
Fix Version/s: 8.1
Assignee: Ted Jones
> Incorrect parameter types in invokeHttp
> ---------------------------------------
>
> Key: TEIIDDES-1570
> URL: https://issues.jboss.org/browse/TEIIDDES-1570
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 8.0
> Reporter: Daniel Susín
> Assignee: Ted Jones
> Fix For: 8.1
>
> Attachments: invokeHttp_parameters.jpg
>
>
> In Designer 8, when you try to import a remote XML file as data source, and create the corresponding view and table, the parameters of invokeHttp in the transformation created automatically are incorrect: 'stream' is assigned a blob datatype and 'result' a boolean one, they have to be manually switched for the transformation to work. Also, stream is not included on the default call, you either have to include it or use named parameters if you want to use the default value.
--
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
13 years, 3 months
[JBoss JIRA] (TEIIDDES-1568) NPEs resulting from null parent mapping nodes on XML Document creation from schema
by Paul Richardson (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1568?page=com.atlassian.jira.plu... ]
Paul Richardson resolved TEIIDDES-1568.
---------------------------------------
Resolution: Done
> NPEs resulting from null parent mapping nodes on XML Document creation from schema
> ----------------------------------------------------------------------------------
>
> Key: TEIIDDES-1568
> URL: https://issues.jboss.org/browse/TEIIDDES-1568
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Affects Versions: 8.1
> Reporter: Barry LaFond
> Assignee: Paul Richardson
> Fix For: 8.1
>
> Attachments: Employees.xsd
>
>
> While trying to create simple XML document for "Employee" from the attached Employees.xsd schema, there were NPE's.
> 1) Import Employees.xsd in to project
> 2) Select "Employee" schema element in explorer and right click "Modeling > Create XML View Documents" (XML Document Model)
> 3) When finished it should create a XML document with mapping classes
> Tracked in Debug and seems the created MappingDocument class does not have it's variable "parent" set which is required to walk the mapping nodes and create children.
> !ENTRY org.teiid.designer.transformation 4 0 2013-01-28 08:29:47.504
> !MESSAGE
> !STACK 0
> java.lang.NullPointerException
> at org.teiid82.sql.impl.xml.MappingDocumentFactory.addNamespace(MappingDocumentFactory.java:66)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createNamespaceAttribute(MappingDocumentFormatter.java:833)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:787)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processChildren(MappingDocumentFormatter.java:1118)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.processNamespaces(MappingDocumentFormatter.java:1198)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createDocumentNode(MappingDocumentFormatter.java:702)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMapping(MappingDocumentFormatter.java:748)
> at org.teiid.designer.transformation.aspects.sql.MappingDocumentFormatter.createMappingString(MappingDocumentFormatter.java:821)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformation(TreeMappingRootSqlAspect.java:285)
> at org.teiid.designer.transformation.aspects.sql.TreeMappingRootSqlAspect.getTransformationInfo(TreeMappingRootSqlAspect.java:333)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addTransformationWords(RuntimeAdapter.java:412)
> at org.teiid.designer.core.metadata.runtime.RuntimeAdapter.addIndexWord(RuntimeAdapter.java:172)
> at org.teiid.designer.core.index.ModelIndexer.addIndexWord(ModelIndexer.java:311)
> at org.teiid.designer.core.index.ModelIndexer.index(ModelIndexer.java:164)
--
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
13 years, 3 months