1 Reply Latest reply on Apr 11, 2013 1:27 PM by Ted Jones

    Redundant DEFAULT Namespaces Generated In Procedures For WSDL import.

    Steve Darnowsky Newbie

       

       

      Using  version 8.1 alpha 2  imported attached wsdl  into Teid Designer. The follwong procedure was generated that violates the rule of one DEFAULT or NODEFAULT namespaces wihtin scope of one XMLElement statement. I am able to edit the procedure to remove the second default and no default nps for now as a workaorund.

       

       

      CREATE VIRTUAL PROCEDURE 

      BEGIN

      SELECT

      XMLELEMENT(NAME "soap:Envelope", XMLNAMESPACES('http://schemas.xmlsoap.org/soap/envelope/' AS soap, DEFAULT 'http://otda.ny.gov/intake/caseinqwsdl/1_0', DEFAULT 'http://otda.ny.gov/intake/caseinquiryin/1_0'), XMLELEMENT(NAME "soap:Header"), XMLELEMENT(NAME "soap:Body", XMLELEMENT(NAME CaseInquiry, XMLELEMENT(NAME CaseNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.CaseNumber), XMLELEMENT(NAME DistrictNumber, XMLNAMESPACES(NO DEFAULT), NYCWMSServiceView.CaseInquiry_request.DistrictNumber)))) AS

      xml_out;

      END

       

      ERROR: At most only one NO DEFAULT or DEFAULT namespace may be specified.