2 Replies Latest reply: Dec 6, 2012 7:52 PM by 978277 RSS

    PL/SQL native web services starting from an XSD ?

      I'm trying to setup an Oracle Native web service in PL/SQL under Oracle running on Red Hat 5 Linux 64-bit.

      We already have native PL/SQL web services running successfully (the database servlet works fine) from a previous project we did, however that project used the following approach:

      1. Start off without an XSD
      2. Hand-code the SQL scripts to create all the Oracle types needed to pass in the XML via web services
      3. Now write the PL/SQL package to use the TYPE for what will be the top-level XML element
      4. Call the native webservices servlet to find out what the WSDL is.

      What I'm trying to do is write a PL/SQL web service that accepts a reasonably-complex XML document as input, and passes back a different XML document as a response. Our new "standard approach" is to use native web services for this.

      So unlike the earlier approach above, I'm trying to start with an XSD instead, as follows:

      1. Write the XSD using Altova XMLSpy.
      2. Edit the XSD to add Oracle XDB extensions such as xdb:SQLType and xdb:SQLName, eg: to control the naming of the types (if I don't do this, RegisterSchema() [below] will generate its own random unique names)
      2. Load it into the Oracle DB using DBMS_XMLSCHEMA.registerSchema (), with gentypes=>TRUE
      3. Create the new PL/SQL package to use the TYPE for the top-level element.
      4. Check the service is OK by retrieving the WSDL back from the database using Internet Explorer

      You'd think this would work reasonably intuitively (I've been coding PL/SQL for over 15 years), but instead it's been very difficult to actually get working. The Oracle TYPEs generated by RegisterSchema() seem to make Oracle webservices very unhappy: even though the XSD loads OK and the TYPEs get created, and the package compiles fine, the WSDL that gets returned by Oracle for this new package is actually gibberish (it's not even syntactically correct) and causes Internet Explorer and SoapUI to complain loudly.

      I've done the usual Googling, but cannot seem to find any articles describing anyone creating a native PL/SQL web service from an XSD that has actually been loaded into the database. Most examples seem to be someone trying to expose an existing stored package (one that has very basic in/out parameters) as a web service. We can do this already no problems.

      Any help would be hugely appreciated..I'm on the verge of giving up and hand-coding all the oracle types manually to get it working.

        • 1. Re: PL/SQL native web services starting from an XSD ?

          Seems that you're following the correct approach.
          Please post a simple test case showing the issue.

          What error(s) are you getting?
          • 2. Re: PL/SQL native web services starting from an XSD ?
            Hi thanks for your fast reply.

            I've put together a test case below:

            lv_schema_name VARCHAR2(300):= 'testcase.xsd';

            lv_schema_doc VARCHAR(32767):='<?xml version="1.0" encoding="UTF-8"?>
            <schema xmlns="http://www.w3.org/2001/XMLSchema"
            elementFormDefault="qualified" version="1.0"
            xdb:mapStringToNCHAR="false" xdb:storeVarrayAsTable="true">
            <element name="root_element" xdb:SQLName="ROOT_ELEMENT" xdb:SQLType="TESTCASE_ROOT_ELEMENT_T">
            <complexType xdb:maintainDOM="false">
            <element name="Loyalty_Status" xdb:SQLName="LOYALTY_STATUS">
            <restriction base="string">
            <enumeration value="immediate"/>
            <enumeration value="wait"/>

            exXSDDoesNotExist EXCEPTION;
            PRAGMA EXCEPTION_INIT (exXSDDoesNotExist, -31000);

            schemaURL => lv_schema_name
            , delete_option => DBMS_XMLSCHEMA.DELETE_CASCADE
            WHEN exXSDDoesNotExist THEN

            schemaurl=> lv_schema_name,
            schemaDoc => lv_schema_doc,
            local => True,
            genTypes => true,
            genbean => FALSE,
            gentables => FALSE


            create or replace package DBPK_WS_TEST is

            PROCEDURE test1 (pi_input in testcase_root_element_t);

            end DBPK_WS_TEST;

            create or replace package body DBPK_WS_TEST is

            PROCEDURE test1 (pi_input in testcase_root_element_t)
            END test1;

            end DBPK_WS_TEST;

            Now if I pull out the WSDL using URL http://myserver:myport/orawsv/myschema/DBPK_WS_TEST/TEST1?wsdl

            I get this:

            <definitions name="TEST1"
            <xsd:schema targetNamespace="http://xmlns.oracle.com/orawsv/ADMIN/DBPK_WS_TEST/TEST1"
            <xsd:element name="TEST1Input">
            <xsd:element name="PI_INPUT-TESTCASE_ROOT_ELEMENT_T-CIN" type="tns:TESTCASE_ROOT_ELEMENT_TType"/>

            <xsd:element name="TEST1Output">
            <xsd:complexType name="TESTCASE_ROOT_ELEMENT_TType">
            <xsd:element name="TESTCASE_ROOT_ELEMENT_T">
            <xsd:element name="LOYALTY_STATUS" type="XDB.tns:XDB$ENUM_T_IntType"/>
            <xsd:complexType name="XDB.XDB$ENUM_T_IntType">
            <xsd:element name="VALUE" type="xsd:hexBinary"/>

            <message name="TEST1InputMessage">
            <part name="parameters" element="tns:TEST1Input"/>

            <message name="TEST1OutputMessage">
            <part name="parameters" element="tns:TEST1Output"/>

            <portType name="TEST1PortType">
            <operation name="TEST1">
            <input message="tns:TEST1InputMessage"/>
            <output message="tns:TEST1OutputMessage"/>

            <binding name="TEST1Binding"
            <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
            <operation name="TEST1">
            <soap:body parts="parameters" use="literal"/>
            <soap:body parts="parameters" use="literal"/>

            <service name="TEST1Service">
            <documentation>Oracle Web Service</documentation>
            <port name="TEST1Port" binding="tns:TEST1Binding">


            The problem is with XDB.XDB$ENUM_T_IntType

            If I try and load this WSDL in something such as SOAPUI, I get the following:

            Source: http://myserver:myport/orawsv/myschema/DBPK_WS_TEST/TEST1?wsdl Error: The value 'XDB.XDB$ENUM_T_IntType' is an invalid name.