Generate Proxy or Server Side stub Problem

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • BillyLiu007

    #1

    Generate Proxy or Server Side stub Problem

    Hi all:
    Its easy for us to use the wdsl.exe to generate a proxy or server side stub
    from the .wsdl file.

    but when .wdsl file its not just one file, it import another .wdsl file and
    schema file, the wsdl.exe cannot generate any outcome.

    I read from the article said its the limitation of the wsdl.exe , but anyone
    know any way to solve the issue, or is there any replacement tools ?
    --
    Can You?You Can.
  • 6kjfsyg02@sneakemail.com

    #2
    Re: Generate Proxy or Server Side stub Problem

    In our case, we included the imported schemas into the WSDL.

    --
    David Mediavilla

    Comment

    • 6kjfsyg02@sneakemail.com

      #3
      Re: Generate Proxy or Server Side stub Problem

      In our case, we included the imported schemas into the WSDL.

      --
      David Mediavilla

      Comment

      • BillyLiu007

        #4
        Re: Generate Proxy or Server Side stub Problem

        yup...you correct..
        actaully, my .wsdl is import the schema file also.
        The problem is that the wsdl.exe has some problem to locate the import file
        path.

        I read from another forum, this guy suggest copy all the wsdl and schema
        files in same directory and use wsdl.exe with all the related files as
        argument, including the schema files. He declared its working, and i haven't
        tried it out yet
        --
        Can You?You Can.


        "6kjfsyg02@snea kemail.com" wrote:
        [color=blue]
        > In our case, we included the imported schemas into the WSDL.
        >
        > --
        > David Mediavilla
        >
        >[/color]

        Comment

        • BillyLiu007

          #5
          Re: Generate Proxy or Server Side stub Problem

          yup...you correct..
          actaully, my .wsdl is import the schema file also.
          The problem is that the wsdl.exe has some problem to locate the import file
          path.

          I read from another forum, this guy suggest copy all the wsdl and schema
          files in same directory and use wsdl.exe with all the related files as
          argument, including the schema files. He declared its working, and i haven't
          tried it out yet
          --
          Can You?You Can.


          "6kjfsyg02@snea kemail.com" wrote:
          [color=blue]
          > In our case, we included the imported schemas into the WSDL.
          >
          > --
          > David Mediavilla
          >
          >[/color]

          Comment

          Working...