February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-301) Queries against web services that aren't running makes Designer inoperative (because of bug in Apache Axis)

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-301?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-864 to TEIIDDES-301: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-301 (was: JBEDSP-864) Component/s: Teiid Integration VDB & Execution (was: Connectors) (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > Queries against web services that aren't running makes Designer inoperative (because of bug in Apache Axis) > ----------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-301 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-301 > Project: Teiid Designer > Issue Type: Bug > Components: Teiid Integration, VDB & Execution > Affects Versions: 7.1 > Environment: 5.5SP3 GA Designer on Linux > Reporter: Greg Haber > Attachments: axis-error.txt, wsTest1_20081211_1.zip > > > When putting together the new 5.5SP3 sales demo, I noticed that if I forgot to start the web service's container before I started Designer, and then tried to query against that web service, I would get an error message (as expected), but if I then started up the web service and retried my query in that same Designer instance, I would get a MetaMatrixException. I would need to shut down Designer and restart it to then be able to successfully query the web service. > I've attached the model project set for those who want to reproduce. The actual web service .aar file and instructions on using it are on JBEDSP-850. > For those trying to reproduce, note that I can only reproduce when the machine running the web service is up and reachable, but the container hosting the web service is not running (you need to get a java.net.ConnectException - if you get an UnknownHostException we do for some reason survive that). > I dug deeper into this and found that the initial exception I was seeing pop up in Designer was not in fact getting logged to the Designer message log. And on Designer's stdout, I saw the messages that I've attached as axis-error.txt. If you look at the exception you'll see that what is happening is that when we try to call printStackTrace on the exception, all sorts of Apache Axis stuff kicks in and the message logging fails. > I traced this issue back to com.metamatrix.connector.xml.soap.SOAPExecutor, where we have in the executeCall method the following: > } catch (AxisFault e) { > throw new ConnectorException(e); > I found that if I changed this to > } catch (AxisFault e) { > throw new ConnectorException(e.getMessage()); > to avoid passing back the AxisFault, then the error message about the java.net.ConnectException would be recorded in the Designer message log, and also that I could start up the web service and then retry my query in Designer successfully (without restarting Designer). > So it looks like we need to look at not only the XML-Relational Connector, but any other connectors that use Axis and throw AxisFault, to make sure we parse out the contents of the AxisFault and return those contents safely back when we throw ConnectorException. > I also thought about opening up a separate JIRA that the core MetaMatrix code should be able to handle when something went funny when we called printStackTrace on a ConnectorException. I ran this by one of the JBDS developers that sits near me, and he said that he thought that it was reasonable to assume that calling printStackTrace on any subclass of java.lang.Exception (such as AxisFault) should just work without having subclass-specific stuff available - so this isn't something we should need to protect against - that this is really poor design in Apache Axis, and since this is an exception to normal Exception behavior he recommended just protecting against this one subclass of Exception (AxisFault) like in my workaround above. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-300) Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-300?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-850 to TEIIDDES-300: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-300 (was: JBEDSP-850) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > Web Service As Relational importer needs to create access patterns and pk-fk pairs to more correctly model how the tables should be queried at run time > ------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-300 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-300 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Environment: 5.5SP3 GA Designer on Linux > Reporter: Greg Haber > Assignee: John Doyle > Attachments: FinancialsDemo_20081130_4.zip, no-parameter-stacktrace.txt, StockQuoteService-ghh.wsdl, StockQuoteService.aar, wsTest1.zip > > > When the Web Service as Relational importer creates a source model, it creates a single request table and one or more response tables to model the web service operation. If there are any required parameters in the web service requests (those which do not contain the property "minOccurs=0") the right way to represent this in MetaMatrix would be via an access pattern. > But the importer does not create such an access pattern on the request tables, which means that if the preview functionality is run against them, it tries to do a query against the table with no parameters specified, resulting in an error from the XML-Relational SOAP connector (stacktrace attached). > The importer should create such an access pattern to more correctly reflect the actual behavior of the web service (and our connector framework). > I'm attaching the model project set for my test, the WSDL for the service (as deployed on my machine), and the .aar file for the actual service (to use just deploy the Axis 2 war from http://www.gtlib.gatech.edu/pub/apache/ws/axis2/1_4_1/axis2-1.4.1-war.zip on a server, and then drop the .aar file in the axis2/WEB-INF/services directory that should exist on your server after deployment). -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-299) The WSDL to relational importer is not creating the correct XPath for a SOAP Array

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-299?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1131 to TEIIDDES-299: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-299 (was: JBEDSP-1131) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > The WSDL to relational importer is not creating the correct XPath for a SOAP Array > ---------------------------------------------------------------------------------- > > Key: TEIIDDES-299 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-299 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > > Note that the namespaces in the doc do not correspond to what the WSDl says they should be. But beyond that, the XPath for the data in the array is not correct, It needs to go one level deeper. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-298) ENHANCEMENT: soap requests should be modeled as procedures

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-298?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-912 to TEIIDDES-298: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-298 (was: JBEDSP-912) Component/s: Modeling (was: Server) Fix Version/s: (was: PostWestport) Affects Version/s: Future (was: 5.5) > ENHANCEMENT: soap requests should be modeled as procedures > ---------------------------------------------------------- > > Key: TEIIDDES-298 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-298 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: Future > Reporter: Steven Hawkins > > Defect Tracker #23657: Currently SOAP request documents are imported as relational tables. This is not very clear from a user perspective. For simple requests, it would be better to import them as a procedure. This defect however cannot be worked until the ability to join on a procedure is implemented, which may happen in 5.0.3. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-297) EResourceImpl And MtkXmiResourceImpl Should Be Refactored To Reduce Code Redundancy

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-297?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-260 to TEIIDDES-297: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-297 (was: JBEDSP-260) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: Future (was: Future Versions) > EResourceImpl And MtkXmiResourceImpl Should Be Refactored To Reduce Code Redundancy > ----------------------------------------------------------------------------------- > > Key: TEIIDDES-297 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-297 > Project: Teiid Designer > Issue Type: Task > Affects Versions: Future > Reporter: Dan Florian > > Both EResourceImpl and MtkXmiResourceImpl extend XMIResourceImpl and implement EmfResource and XResource. Many of their methods are implemented exactly the same. Some methods have subtle differences (is this intentional or was one updated and not the other). Also, each class has their own versions of XMIHelperImpl, XMISaveImpl, SAXXMIHandler, ResourceFactoryImpl, and XMILoadImpl. And each of these supporting classes have a lot of duplicate code. A new design will help maintenance of these resource classes. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-296) XSD to Relational importer fails on simple schema import.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-296?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-949 to TEIIDDES-296: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-296 (was: JBEDSP-949) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.3) > XSD to Relational importer fails on simple schema import. > --------------------------------------------------------- > > Key: TEIIDDES-296 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-296 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Environment: Linux Designer on RHEL-CSB > Reporter: John Doyle > Assignee: John Doyle > Attachments: XSDImportFailure.zip > > > Use the XML Schema as relational source model importer on pos.xsd in the attached model set. It produces this exception when generating the model. > java.lang.NullPointerException > at org.eclipse.emf.ecore.impl.BasicEObjectImpl.eDynamicSet(BasicEObjectImpl.java:558) > at com.metamatrix.modeler.internal.core.ObjectExtension.eDynamicSet(ObjectExtension.java:90) > at com.metamatrix.modeler.modelgenerator.xml.modelextension.impl.BaseXMLRelationalExtensionManagerImpl.setNamespacePrefixesAttribute(BaseXMLRelationalExtensionManagerImpl.java:38) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNamespacePrefixesAttribute(XmlSchemaAsRelationalModelProcessor.java:327) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setTableNamespacePrefixes(XmlSchemaAsRelationalModelProcessor.java:273) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewTable(XmlSchemaAsRelationalModelProcessor.java:96) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.processNewEntity(XmlSchemaAsRelationalModelProcessor.java:75) > at com.metamatrix.modeler.modelgenerator.xml.wizards.jdbc.XmlSchemaAsRelationalModelProcessor.setNameAndNameInSource(XmlSchemaAsRelationalModelProcessor.java:65) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.createNewObject(RelationalModelProcessorImpl.java:1058) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.performExecute(RelationalModelProcessorImpl.java:804) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl$1.run(RelationalModelProcessorImpl.java:326) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:547) > at com.metamatrix.modeler.internal.core.ModelEditorImpl.executeAsTransaction(ModelEditorImpl.java:587) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:333) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.executeWithinTransaction(RelationalModelProcessorImpl.java:311) > at com.metamatrix.modeler.jdbc.relational.impl.RelationalModelProcessorImpl.execute(RelationalModelProcessorImpl.java:302) > at com.metamatrix.modeler.modelgenerator.xml.wizards.XsdAsRelationalImportWizard$1.run(XsdAsRelationalImportWizard.java:504) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113) -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-295) "EResourceImpl" class must implement "XResource" interface

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-295?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-407 to TEIIDDES-295: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-295 (was: JBEDSP-407) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: Westport) > "EResourceImpl" class must implement "XResource" interface > ---------------------------------------------------------- > > Key: TEIIDDES-295 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-295 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Ramesh Reddy > Assignee: Johnny Verhaeg > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > Currently "EResourceImpl" does not implement XResource, and thus fail to look up the UUID. Lack of this creates a Stack Over Flow, it it tries to find the id using the URL fragment and calls itself. To get over the hump, I putting in the interface on the object and returning null, however the implementation is still due. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-293) WSDL to Relational Importer: WSDL causes NPE when generating model.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-293?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-333 to TEIIDDES-293: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-293 (was: JBEDSP-333) Component/s: Import/Export (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.2) (was: 5.5.1) (was: 5.5) > WSDL to Relational Importer: WSDL causes NPE when generating model. > ------------------------------------------------------------------- > > Key: TEIIDDES-293 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-293 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Attachments: TmsWebService.wsdl > > > The attached WSDL causes an NPE when the model objects are being created. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-294) Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-294?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-379 to TEIIDDES-294: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-294 (was: JBEDSP-379) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5) > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long > ----------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-294 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-294 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: Michael Walker > Assignee: Barry LaFond > Attachments: queryplantruncation.JPG, queryplantruncation2.JPG > > > Query Plan Viewer in Designer does not fully display source queries in the bottom panel if it is long. See screenshot for example. First screenshot shows the beginning of the source query, second screenshot shows that the source query is truncated when I scroll all the way to the right. > We should show the entire query. > This problem also occurs on Access nodes on the top-half of the query planner. However, you can double-click to view the entire query. This double-click capability is not available on the bottom half for some reason. Perhaps we should add it. > There are some cases where source queries are not displayed in the top-half (query plan screen) but do appear in the bottom half only. In those cases, there's no way to view the entire source query using this editor. Workaround is to view the XML query plan. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-292) WSDL to Relational Importer should be smarter about column names.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-292?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-241 to TEIIDDES-292: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-292 (was: JBEDSP-241) Component/s: (was: Designer) Fix Version/s: (was: Westport) Affects Version/s: 7.1 (was: 5.5.1) (was: 5.5) (was: 5.5.2) > WSDL to Relational Importer should be smarter about column names. > ----------------------------------------------------------------- > > Key: TEIIDDES-292 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-292 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > Attachments: ndfdXML.wsdl > > > With some WSDL the WSDL to Relational Importer will default a column name to text, when it should provide a name for the column. This can be especially problematic when this happens more than once per table, in that case we create a model that does not validate. See the attached schema. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2010