Beehive
  1. Beehive
  2. BEEHIVE-596

WebParamRpcLiteralSample's wsdl is not valid

    Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: V1Beta, v1m1
    • Fix Version/s: None
    • Component/s: Web Services (181)
    • Labels:
      None

      Description

      WSM sample's WebParamRpcLiteralSample generates a wsdl that is not compliant with the BP 1.0:

      R2205 A wsdl:binding in a DESCRIPTION MUST refer, in each of its soapbind:header, soapbind:headerfault and soapbind:fault elements, only to wsdl:part element(s) that have been defined using the element attribute.

      The http://localhost:8080/wsm-samplesWS/web/webparam/WebParamRpcLiteralSample.jws?wsdl

      should not use type in

      wsdl:message name="sayHelloInHeaderRequest">
      <wsdl:part name="namein" type="xsd:string"/>
      </wsdl:message>

      it should be an element.

        Issue Links

          Activity

          Hide
          Jeremiah Johnson added a comment -

          Updated the description to note that it is the header message part that is incorrect, not the body message part.

          Show
          Jeremiah Johnson added a comment - Updated the description to note that it is the header message part that is incorrect, not the body message part.
          Hide
          daryoush mehrtash added a comment -

          I applied the patch to my local axis build and tried it out. It appears to have fixed some of the problems with the WSDL. The WSDL compiler is still having issues with the generated wsdl, I will need to dig deeper into this bug.

          This bug and fix for it should not be a showstopper for the V1 release.

          Show
          daryoush mehrtash added a comment - I applied the patch to my local axis build and tried it out. It appears to have fixed some of the problems with the WSDL. The WSDL compiler is still having issues with the generated wsdl, I will need to dig deeper into this bug. This bug and fix for it should not be a showstopper for the V1 release.
          Hide
          Jongjin Choi added a comment -

          I tested the wsdl (http://localhost:8080/wsm-samplesWS/web/webparam/WebParamRpcLiteralSample.jws?wsdl
          ) using patched axis.

          The wscompile still complains about wsdl like this:
          (I used the wscompile included in SUN Java Server 2005Q1, but got similar error under JWSDP 1.5)
          -----------------------------
          D:\tests\beehive\BEEHIVE-599>c:\Sun\AppServer\bin\wscompile.bat -gen -d generated -Xprintstacktrace config-wsdl-rpclit.xml
          "namein" specified in the parameterOrder attribute of message "sayHelloInHeader" is not a valid part of the message.
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processParameterOrder(WSDLModelerBase.java:2101)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperationRPCLiteralStyle(WSDLModelerBase.java:2316)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperation(WSDLModelerBase.java:905)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processPort(WSDLModelerBase.java:763)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processService(WSDLModelerBase.java:519)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.internalBuildModel(WSDLModelerBase.java:354)
          at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:238)
          at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88)
          at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63)
          at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714)

          at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43)
          at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22)
          error: "namein" specified in the parameterOrder attribute of message "sayHelloInHeader" is not a valid part of the message.
          --------------------------------

          I also tested using SUN's JAX-RPC 2.0EA. I generated the WSDL from beehive samples source, the genearted wsdl from JAX-RPC 2.0EA was not processed using wscompile with similar error.

          I guess that SUN's wscompile (in JWSDP 1.5) is not ready for this kind of wsdl.

          Show
          Jongjin Choi added a comment - I tested the wsdl ( http://localhost:8080/wsm-samplesWS/web/webparam/WebParamRpcLiteralSample.jws?wsdl ) using patched axis. The wscompile still complains about wsdl like this: (I used the wscompile included in SUN Java Server 2005Q1, but got similar error under JWSDP 1.5) ----------------------------- D:\tests\beehive\ BEEHIVE-599 >c:\Sun\AppServer\bin\wscompile.bat -gen -d generated -Xprintstacktrace config-wsdl-rpclit.xml "namein" specified in the parameterOrder attribute of message "sayHelloInHeader" is not a valid part of the message. at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processParameterOrder(WSDLModelerBase.java:2101) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperationRPCLiteralStyle(WSDLModelerBase.java:2316) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processSOAPOperation(WSDLModelerBase.java:905) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processPort(WSDLModelerBase.java:763) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.processService(WSDLModelerBase.java:519) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.internalBuildModel(WSDLModelerBase.java:354) at com.sun.xml.rpc.processor.modeler.wsdl.WSDLModelerBase.buildModel(WSDLModelerBase.java:238) at com.sun.xml.rpc.processor.config.ModelInfo.buildModel(ModelInfo.java:88) at com.sun.xml.rpc.processor.Processor.runModeler(Processor.java:63) at com.sun.xml.rpc.tools.wscompile.CompileTool.run(CompileTool.java:714) at com.sun.xml.rpc.util.ToolBase.run(ToolBase.java:43) at com.sun.xml.rpc.tools.wscompile.Main.main(Main.java:22) error: "namein" specified in the parameterOrder attribute of message "sayHelloInHeader" is not a valid part of the message. -------------------------------- I also tested using SUN's JAX-RPC 2.0EA. I generated the WSDL from beehive samples source, the genearted wsdl from JAX-RPC 2.0EA was not processed using wscompile with similar error. I guess that SUN's wscompile (in JWSDP 1.5) is not ready for this kind of wsdl.
          Hide
          Jongjin Choi added a comment -

          WS-I BP 1.0 R2205 patch for Axis

          Show
          Jongjin Choi added a comment - WS-I BP 1.0 R2205 patch for Axis
          Hide
          Jongjin Choi added a comment -

          Daryoush,

          I made a WS-I R-2205 patch for Axis.
          I am doing all-tests(i.e. DRT in Beehive term) for Axis now.
          If this meets our currents need, I'll apply it to axis with normal process.
          Pls, check the generated wsdl.
          Patch will be attached.

          Show
          Jongjin Choi added a comment - Daryoush, I made a WS-I R-2205 patch for Axis. I am doing all-tests(i.e. DRT in Beehive term) for Axis now. If this meets our currents need, I'll apply it to axis with normal process. Pls, check the generated wsdl. Patch will be attached.
          Hide
          Jeremiah Johnson added a comment -

          Here is a link to the message in the mail archive to make it easy to check for follow-ups: http://marc.theaimsgroup.com/?l=axis-dev&m=111516315320440&w=2

          Show
          Jeremiah Johnson added a comment - Here is a link to the message in the mail archive to make it easy to check for follow-ups: http://marc.theaimsgroup.com/?l=axis-dev&m=111516315320440&w=2

            People

            • Assignee:
              Unassigned
              Reporter:
              daryoush mehrtash
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development