[teiid-designer-issues] [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

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).