4 Replies Latest reply on Apr 11, 2002 6:49 AM by 3004

    weblogic client + WASP server

    3004

      Hello,

      I am trying to make weblogic talk to WASP server (www.systinet.com). Attached
      is a WSDL that WASP produced. It generates

      weblogic.xml.schema.binding.BindingException: schema error - with nested excepti
      on:
      [weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http
      ://idoox.com/containers']:ns1:List due to lack of an import statement for namesp
      ace http://idoox.com/containers]
      at weblogic.xml.schema.binding.internal.codegen.SchemaInspector.createDe
      scriptors(SchemaInspector.java:165)
      at weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compile
      r.java:201)
      at weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addAllType
      sInSchemas(XSDTypeMappingBuilder.java:116)
      at weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSc
      hemas(TypeMappingBuilderBase.java:246)
      at weblogic.ant.taskdefs.webservices.autotype.WSDLAutoTyper.run(WSDLAuto
      Typer.java:71)
      at weblogic.ant.taskdefs.webservices.clientgen.WSDLClientGen.run(WSDLCli
      entGen.java:48)
      at weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(Cli
      entGenTask.java:119)

      Any idea what might be wrong?

      What is so interesting about WASP is that apparently they know how to pack a List
      of any java objects into SOAP messages. Look for type="anyType" at http://www.systinet.com/containers.
      How would weblogic handle that?

      Regards,
      Aleksey
      [MOP.wsdl]
        • 1. Re: weblogic client + WASP server
          3004
          It seems the schema in the WSDL types section is incomplete.
          [http://idoox.com/containers]:List is used by the schema, but it
          is not imported.

          I think 7.0 GA supports List (Scott can you confirm this).

          regards,
          -manoj



          "Aleksey" <zander@objectstorm.net> wrote in message
          news:3cb350e9@newsgroups.bea.com...
          >
          Hello,

          I am trying to make weblogic talk to WASP server (www.systinet.com).
          Attached
          is a WSDL that WASP produced. It generates

          weblogic.xml.schema.binding.BindingException: schema error - with nested
          excepti
          on:
          [weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http> ://idoox.com/containers':ns1:List due to lack of an import statement for
          namesp
          ace http://idoox.com/containers]
          at
          weblogic.xml.schema.binding.internal.codegen.SchemaInspector.createDe
          scriptors(SchemaInspector.java:165)
          at
          weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compile
          r.java:201)
          at
          weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addAllType
          sInSchemas(XSDTypeMappingBuilder.java:116)
          at
          weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSc
          hemas(TypeMappingBuilderBase.java:246)
          at
          weblogic.ant.taskdefs.webservices.autotype.WSDLAutoTyper.run(WSDLAuto
          Typer.java:71)
          at
          weblogic.ant.taskdefs.webservices.clientgen.WSDLClientGen.run(WSDLCli
          entGen.java:48)
          at
          weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(Cli
          entGenTask.java:119)

          Any idea what might be wrong?

          What is so interesting about WASP is that apparently they know how to pack
          a List
          of any java objects into SOAP messages. Look for type="anyType" at
          http://www.systinet.com/containers.
          How would weblogic handle that?

          Regards,
          Aleksey
          • 2. Re: weblogic client + WASP server
            3004
            Yes, The schema is not valid. In order to use a type from another
            schema, you must <import> that schema. Most products now handle this
            correctly, though I'm not sure you could say the same 6 months ago.

            List, ArrayList, LinkedList, and Vector are supported in the GA
            release.

            --Scott

            In article <3cb46476$1@newsgroups.bea.com>,
            manoj cheenath <manojc@bea.com> wrote:
            It seems the schema in the WSDL types section is incomplete.
            [http://idoox.com/containers]:List is used by the schema, but it
            is not imported.

            I think 7.0 GA supports List (Scott can you confirm this).

            regards,
            -manoj



            "Aleksey" <zander@objectstorm.net> wrote in message
            news:3cb350e9@newsgroups.bea.com...
            Hello,

            I am trying to make weblogic talk to WASP server (www.systinet.com).
            Attached
            is a WSDL that WASP produced. It generates

            weblogic.xml.schema.binding.BindingException: schema error - with nested
            excepti
            on:
            [weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http>> ://idoox.com/containers':ns1:List due to lack of an import statement for
            namesp
            ace http://idoox.com/containers]
            at
            weblogic.xml.schema.binding.internal.codegen.SchemaInspector.createDe
            scriptors(SchemaInspector.java:165)
            at
            weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compile
            r.java:201)
            at
            weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addAllType
            sInSchemas(XSDTypeMappingBuilder.java:116)
            at
            weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSc
            hemas(TypeMappingBuilderBase.java:246)
            at
            weblogic.ant.taskdefs.webservices.autotype.WSDLAutoTyper.run(WSDLAuto
            Typer.java:71)
            at
            weblogic.ant.taskdefs.webservices.clientgen.WSDLClientGen.run(WSDLCli
            entGen.java:48)
            at
            weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(Cli
            entGenTask.java:119)

            Any idea what might be wrong?

            What is so interesting about WASP is that apparently they know how to pack
            a List
            of any java objects into SOAP messages. Look for type="anyType" at
            http://www.systinet.com/containers.
            How would weblogic handle that?

            Regards,
            Aleksey
            • 3. Re: weblogic client + WASP server
              3004

              So what <import> statement should look like?

              I actually copied over List defenition but now I am getting
              weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http://xml.apache.org/xml-soap']:ns2:Map
              due to lack of an import statement for namespace http://xml.apache.org/xml-soap

              Unfortunatelly I couldn't get schema defenition for apache xml-soap. What do I
              do?

              Anyhow attached is a WSDL that you might use to test compiler in 7.0 GA. 7.0b
              cannot handle it. It generated some weird "convenience method" that it cannot
              compile.




              zieg@bea.com (Scott Ziegler) wrote:
              Yes, The schema is not valid. In order to use a type from another
              schema, you must <import> that schema. Most products now handle this
              correctly, though I'm not sure you could say the same 6 months ago.

              List, ArrayList, LinkedList, and Vector are supported in the GA
              release.

              --Scott

              In article <3cb46476$1@newsgroups.bea.com>,
              manoj cheenath <manojc@bea.com> wrote:
              It seems the schema in the WSDL types section is incomplete.
              [http://idoox.com/containers]:List is used by the schema, but it
              is not imported.

              I think 7.0 GA supports List (Scott can you confirm this).

              regards,
              -manoj



              "Aleksey" <zander@objectstorm.net> wrote in message
              news:3cb350e9@newsgroups.bea.com...
              Hello,

              I am trying to make weblogic talk to WASP server (www.systinet.com).
              Attached
              is a WSDL that WASP produced. It generates

              weblogic.xml.schema.binding.BindingException: schema error - with
              nested
              excepti
              on:
              [weblogic.xml.schema.model.XSDException: Unable to resolve definition
              for>>['http>>> ://idoox.com/containers':ns1:List due to lack of an import statement
              for
              namesp
              ace http://idoox.com/containers]
              at
              weblogic.xml.schema.binding.internal.codegen.SchemaInspector.createDe
              scriptors(SchemaInspector.java:165)
              at
              weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compile
              r.java:201)
              at
              weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addAllType
              sInSchemas(XSDTypeMappingBuilder.java:116)
              at
              weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSc
              hemas(TypeMappingBuilderBase.java:246)
              at
              weblogic.ant.taskdefs.webservices.autotype.WSDLAutoTyper.run(WSDLAuto
              Typer.java:71)
              at
              weblogic.ant.taskdefs.webservices.clientgen.WSDLClientGen.run(WSDLCli
              entGen.java:48)
              at
              weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(Cli
              entGenTask.java:119)

              Any idea what might be wrong?

              What is so interesting about WASP is that apparently they know how
              to pack
              a List
              of any java objects into SOAP messages. Look for type="anyType" at
              http://www.systinet.com/containers.
              How would weblogic handle that?

              Regards,
              Aleksey
              [Persistence.wsdl]
              • 4. Re: weblogic client + WASP server
                3004
                See

                http://www.w3.org/TR/xmlschema-1/#composition-schemaImport

                for information on import.

                Provided you are importing a schema from the same wsdl, you can just
                do something like:

                <xsd:import namespace="http://tempuri.org/" />

                If the schema is not in the same wsdl, ideally you would provide a
                schemaLocation attribute.

                --Scott



                In article <3cb47a52$1@newsgroups.bea.com>,
                Aleksey <zander@objectstorm.net> wrote:
                -=-=-=-=-=-


                So what <import> statement should look like?

                I actually copied over List defenition but now I am getting
                weblogic.xml.schema.model.XSDException: Unable to resolve definition for ['http://xml.apache.org/xml-soap']:ns2:Map
                due to lack of an import statement for namespace http://xml.apache.org/xml-soap

                Unfortunatelly I couldn't get schema defenition for apache xml-soap. What do I
                do?

                Anyhow attached is a WSDL that you might use to test compiler in 7.0 GA. 7.0b
                cannot handle it. It generated some weird "convenience method" that it cannot
                compile.




                zieg@bea.com (Scott Ziegler) wrote:
                Yes, The schema is not valid. In order to use a type from another
                schema, you must <import> that schema. Most products now handle this
                correctly, though I'm not sure you could say the same 6 months ago.

                List, ArrayList, LinkedList, and Vector are supported in the GA
                release.

                --Scott

                In article <3cb46476$1@newsgroups.bea.com>,
                manoj cheenath <manojc@bea.com> wrote:
                It seems the schema in the WSDL types section is incomplete.
                [http://idoox.com/containers]:List is used by the schema, but it
                is not imported.

                I think 7.0 GA supports List (Scott can you confirm this).

                regards,
                -manoj



                "Aleksey" <zander@objectstorm.net> wrote in message
                news:3cb350e9@newsgroups.bea.com...
                Hello,

                I am trying to make weblogic talk to WASP server (www.systinet.com).
                Attached
                is a WSDL that WASP produced. It generates

                weblogic.xml.schema.binding.BindingException: schema error - with
                nested
                excepti
                on:
                [weblogic.xml.schema.model.XSDException: Unable to resolve definition
                for>>>['http>>>> ://idoox.com/containers':ns1:List due to lack of an import statement
                for
                namesp
                ace http://idoox.com/containers]
                at
                weblogic.xml.schema.binding.internal.codegen.SchemaInspector.createDe
                scriptors(SchemaInspector.java:165)
                at
                weblogic.xml.schema.binding.internal.codegen.Compiler.compile(Compile
                r.java:201)
                at
                weblogic.xml.schema.binding.internal.XSDTypeMappingBuilder.addAllType
                sInSchemas(XSDTypeMappingBuilder.java:116)
                at
                weblogic.xml.schema.binding.internal.TypeMappingBuilderBase.processSc
                hemas(TypeMappingBuilderBase.java:246)
                at
                weblogic.ant.taskdefs.webservices.autotype.WSDLAutoTyper.run(WSDLAuto
                Typer.java:71)
                at
                weblogic.ant.taskdefs.webservices.clientgen.WSDLClientGen.run(WSDLCli
                entGen.java:48)
                at
                weblogic.ant.taskdefs.webservices.clientgen.ClientGenTask.execute(Cli
                entGenTask.java:119)

                Any idea what might be wrong?

                What is so interesting about WASP is that apparently they know how
                to pack
                a List
                of any java objects into SOAP messages. Look for type="anyType" at
                http://www.systinet.com/containers.
                How would weblogic handle that?

                Regards,
                Aleksey
                -=-=-=-=-=-
                <?xml version='1.0'?>
                <definitions name='com.objectstorm.mop.Persistence' targetNamespace='http://objectstorm.net/mop/'
                xmlns:mime='http://schemas.xmlsoap.org/wsdl/mime/'
                xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
                xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'
                xmlns:ns0='http://objectstorm.net/mop/'
                xmlns:ns2='http://xml.apache.org/xml-soap'
                xmlns:xsd='http://www.w3.org/2001/XMLSchema'
                xmlns:http='http://schemas.xmlsoap.org/wsdl/http/'
                xmlns='http://schemas.xmlsoap.org/wsdl/'
                xmlns:SOAP-ENC='http://schemas.xmlsoap.org/soap/encoding/'>

                <types>
                <xsd:schema targetNamespace="http://objectstorm.net/mop/">

                <xsd:complexType name="List">
                <xsd:sequence>
                <xsd:element name="item" minOccurs="0" maxOccurs="unbounded" type="xsd:anyType" />
                </xsd:sequence>
                </xsd:complexType>

                <xsd:element name="QuerySpec">
                <xsd:complexType>
                <xsd:sequence>
                <xsd:element name="sortOrderings" minOccurs="0" maxOccurs="1" type="ns0:List"/>
                <xsd:element name="fetchStart" minOccurs="0" maxOccurs="1" type="xsd:int"/>
                <xsd:element name="locksObjects" minOccurs="0" maxOccurs="1" type="xsd:boolean"/>
                <xsd:element name="attributes" minOccurs="0" maxOccurs="1" type="ns0:List"/>
                <xsd:element name="fetchUnique" minOccurs="0" maxOccurs="1" type="xsd:boolean"/>
                <xsd:element name="entityName" minOccurs="1" maxOccurs="1" type="xsd:string"/>
                <xsd:element name="groupBy" minOccurs="0" maxOccurs="1" type="ns0:List"/>
                <xsd:element name="fetchLimit" minOccurs="0" maxOccurs="1" type="xsd:int"/>
                <xsd:element name="useModelPrefetches" minOccurs="0" maxOccurs="1" type="xsd:boolean"/>
                <xsd:element name="qualifier" minOccurs="0" maxOccurs="1" type="ns0:Qualifier"/>
                <xsd:element name="prefetchingRelationships" minOccurs="0" maxOccurs="1" type="ns0:List"/>
                </xsd:sequence>
                </xsd:complexType>
                </xsd:element>
                <xsd:complexType name="Qualifier">
                </xsd:complexType>
                </xsd:schema>
                </types>

                <message name='PersistenceException_Fault'>
                <part name='PersistenceException' type='xsd:string'/>
                </message>

                <message name='Persistence_objectsWithQuerySpec_Request'>
                <part name='spec' type='ns0:QuerySpec'/>
                </message>
                <message name='Persistence_objectsWithQuerySpec_Response'>
                <part name='response' type='ns0:List'/>
                </message>

                <message name='Persistence_insertObjects_2_Request'>
                <part name='list' type='ns0:List'/>
                </message>
                <message name='Persistence_insertObjects_2_Response'/>
                <message name='Persistence_deleteObjects_1_Request'>
                <part name='list' type='ns0:List'/>
                </message>
                <message name='Persistence_deleteObjects_1_Response'/>
                <message name='Persistence_updateObjects_3_Request'>
                <part name='list' type='ns0:List'/>
                </message>
                <message name='Persistence_updateObjects_3_Response'/>

                <message name='Persistence_executeRawSQL_4_Request'>
                <part name='entityName' type='xsd:string'/>
                <part name='rawSQL' type='xsd:string'/>
                </message>
                <message name='Persistence_executeRawSQL_4_Response'>
                <part name='response' type='ns0:List'/>
                </message>
                <portType name='Persistence'>
                <operation name='deleteObjects' parameterOrder='list'>
                <input name='deleteObjects_1_input' message='ns0:Persistence_deleteObjects_1_Request'/>
                <output name='deleteObjects_1_output' message='ns0:Persistence_deleteObjects_1_Response'/>
                <fault name='deleteObjects_1_fault1' message='ns0:PersistenceException_Fault'/>
                </operation>
                <operation name='updateObjects' parameterOrder='list'>
                <input name='updateObjects_3_input' message='ns0:Persistence_updateObjects_3_Request'/>
                <output name='updateObjects_3_output' message='ns0:Persistence_updateObjects_3_Response'/>
                <fault name='updateObjects_3_fault1' message='ns0:PersistenceException_Fault'/>
                </operation>
                <operation name='executeRawSQL' parameterOrder='entityName rawSQL'>
                <input name='executeRawSQL_4_input' message='ns0:Persistence_executeRawSQL_4_Request'/>
                <output name='executeRawSQL_4_output' message='ns0:Persistence_executeRawSQL_4_Response'/>
                <fault name='executeRawSQL_4_fault1' message='ns0:PersistenceException_Fault'/>
                </operation>
                <operation name='insertObjects' parameterOrder='list'>
                <input name='insertObjects_2_input' message='ns0:Persistence_insertObjects_2_Request'/>
                <output name='insertObjects_2_output' message='ns0:Persistence_insertObjects_2_Response'/>
                <fault name='insertObjects_2_fault1' message='ns0:PersistenceException_Fault'/>
                </operation>
                <operation name='objectsWithQuerySpec' parameterOrder='spec'>
                <input name='objectsWithQuerySpec' message='ns0:Persistence_objectsWithQuerySpec_Request'/>
                <output name='objectsWithQuerySpec' message='ns0:Persistence_objectsWithQuerySpec_Response'/>
                <fault name='objectsWithQuerySpec_fault1' message='ns0:PersistenceException_Fault'/>
                </operation>
                </portType>
                     <binding name="Persistence" type="ns0:Persistence">
                          <soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="document"/>

                <operation name='deleteObjects' >
                               <soap:operation soapAction="http://localhost:8080/snoop" style="document"/>
                <input>
                                    <soap:body use="literal"/>
                               </input>
                               <output>
                                    <soap:body use="literal"/>
                               </output>
                </operation>
                <operation name='updateObjects'>
                               <soap:operation soapAction="http://localhost:8080/snoop" style="document"/>
                <input>
                                    <soap:body use="literal"/>
                               </input>
                               <output>
                                    <soap:body use="literal"/>
                               </output>
                </operation>
                <operation name='executeRawSQL' >
                               <soap:operation soapAction="http://localhost:8080/snoop" style="document"/>
                <input>
                                    <soap:body use="literal"/>
                               </input>
                               <output>
                                    <soap:body use="literal"/>
                               </output>
                </operation>
                <operation name='insertObjects'>
                               <soap:operation soapAction="http://localhost:8080/snoop" style="document"/>
                <input>
                                    <soap:body use="literal"/>
                               </input>
                               <output>
                                    <soap:body use="literal"/>
                               </output>
                </operation>
                <operation name='objectsWithQuerySpec'>
                               <soap:operation soapAction="http://localhost:8080/snoop" style="document"/>
                <input>
                                    <soap:body use="literal"/>
                               </input>
                               <output>
                                    <soap:body use="literal"/>
                               </output>
                </operation>
                </binding>

                     <service name="MOP">
                          <documentation>ObjectStorm XMLPort</documentation>
                          <port name="MOPSoap" binding="ns0:Persistence">
                               <soap:address location="http://localhost:8080/snoop"/>
                          </port>
                     </service>
                </definitions>

                -=-=-=-=-=-