[ https://issues.jboss.org/browse/TEIIDDES-1410?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1410: ----------------------------------- Description: I've got a deployed WAR which queries just fine through soapUI. I've modeled it in Designer and am trying to preview the data. All I get is column headings. After deploying the VDB, I get the same results from SQuirreL when I query: SELECT * FROM (EXEC getSuppInfo(SUPPLIER_ID='S105', PART_ID='P305')) c The soapUI request and response are below. This request: {code:xml} <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sup="http://www.metamatrix.com/SuppInfo_Input"> <soapenv:Header/> <soapenv:Body> <sup:SuppInfo_Input> <!--Optional:--> <SUPPLIER_ID>S104</SUPPLIER_ID> <!--Optional:--> <PART_ID>P305</PART_ID> </sup:SuppInfo_Input> </soapenv:Body> </soapenv:Envelope> Should respond with: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <SuppInfo_Output:SuppInfo_Output xmlns:Q1="http://www.metamatrix.com/metamodels/SimpleDatatypes-insta... xmlnss="http://www.w3.org/2001/XMLSchema" xmlnssi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SuppInfo_Output="http://www.metamatrix.com/SuppInfo_Output&quo... <SuppInfo_Output_Instance> <SUPPLIER_ID>S104</SUPPLIER_ID> <SUPPLIER_NAME>Adams</SUPPLIER_NAME> <SUPPLIER_STATUS>10</SUPPLIER_STATUS> <SUPPLIER_CITY>Atlanta</SUPPLIER_CITY> <SUPPLIER_STATE>GA</SUPPLIER_STATE> <PART_ID>P305</PART_ID> <QUANTITY>100</QUANTITY> <SHIPPER_ID>20</SHIPPER_ID> </SuppInfo_Output_Instance> </SuppInfo_Output:SuppInfo_Output> </soap:Body> </soap:Envelope> {code} Ted Jones sees a problem with namespace declarations. was: I've got a deployed WAR which queries just fine through soapUI. I've modeled it in Designer and am trying to preview the data. All I get is column headings. After deploying the VDB, I get the same results from SQuirreL when I query: SELECT * FROM (EXEC getSuppInfo(SUPPLIER_ID='S105', PART_ID='P305')) c The soapUI request and response are below. This request: <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:sup="http://www.metamatrix.com/SuppInfo_Input"> <soapenv:Header/> <soapenv:Body> <sup:SuppInfo_Input> <!--Optional:--> <SUPPLIER_ID>S104</SUPPLIER_ID> <!--Optional:--> <PART_ID>P305</PART_ID> </sup:SuppInfo_Input> </soapenv:Body> </soapenv:Envelope> Should respond with: <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <SuppInfo_Output:SuppInfo_Output xmlns:Q1="http://www.metamatrix.com/metamodels/SimpleDatatypes-insta... xmlnss="http://www.w3.org/2001/XMLSchema" xmlnssi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SuppInfo_Output="http://www.metamatrix.com/SuppInfo_Output&quo... <SuppInfo_Output_Instance> <SUPPLIER_ID>S104</SUPPLIER_ID> <SUPPLIER_NAME>Adams</SUPPLIER_NAME> <SUPPLIER_STATUS>10</SUPPLIER_STATUS> <SUPPLIER_CITY>Atlanta</SUPPLIER_CITY> <SUPPLIER_STATE>GA</SUPPLIER_STATE> <PART_ID>P305</PART_ID> <QUANTITY>100</QUANTITY> <SHIPPER_ID>20</SHIPPER_ID> </SuppInfo_Output_Instance> </SuppInfo_Output:SuppInfo_Output> </soap:Body> </soap:Envelope> Ted Jones sees a problem with namespace declarations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1410?page=com.atlassian.jira.plu... ] Paul Richardson edited comment on TEIIDDES-1410 at 6/6/12 9:24 AM: ------------------------------------------------------------------- Similar problem found when recreating the VDB (by importing from the wsdl) from the US States example. see https://issues.jboss.org/browse/TEIIDDES-1393?focusedCommentId=12695438&a... was (Author: phantomjinx): Similar problem found when recreating the VDB (by importing from the wsdl) from the US Status example. see https://issues.jboss.org/browse/TEIIDDES-1393?focusedCommentId=12695438&a... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1410?page=com.atlassian.jira.plu... ] RH Bugzilla Integration updated TEIIDDES-1410: ---------------------------------------------- Bugzilla Update: Perform -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1410?page=com.atlassian.jira.plu... ] Ted Jones resolved TEIIDDES-1410. --------------------------------- Resolution: Done Changed to use the schema element name and the message part namespace as default for the request procedure. Also changed the response to prefix qualify namespaces due to some elements having namespaces and some not. The default namespace usage was causing issues in this scenario and always qualifying namespaces with prefixes avoids the problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TEIIDDES-1410?page=com.atlassian.jira.plu... ] RH Bugzilla Integration commented on TEIIDDES-1410: --------------------------------------------------- Van Halbert <vhalbert(a)redhat.com&gt; changed the Status of [bug 829735|https://bugzilla.redhat.com/show_bug.cgi?id=829735] from MODIFIED to ASSIGNED -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira