How to build a WCF service from an existing WSDL

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

    How to build a WCF service from an existing WSDL

    I have an existing ASMX web service produced WSDL. I am trying to upgrade
    the ASMX to WCF. The client side applications are already deployed on
    customers sites. We are definitely not able to change the WSDL in any way.
    Therefore I am thinking maybe the right approprach is to start a WCF service
    from an existing WSDL.
    What are the steps then?
    I know how to create a WCF from an interface, which is the normal way, but I
    cannot make the service talking to the clients, because the generated WSDL
    from WCF are very different from the original WSDL that I published to
    client application before.
    Thanks.
    Hao


  • Spam Catcher

    #2
    Re: How to build a WCF service from an existing WSDL

    "Hao" <Hao@newsgroup. nospamwrote in
    news:#s2yN5S#HH A.748@TK2MSFTNG P04.phx.gbl:
    I have an existing ASMX web service produced WSDL. I am trying to
    upgrade the ASMX to WCF. The client side applications are already
    deployed on customers sites. We are definitely not able to change the
    WSDL in any way. Therefore I am thinking maybe the right approprach is
    to start a WCF service from an existing WSDL.
    What are the steps then?
    I would stick with ASMX.

    Comment

    • Hao

      #3
      Re: How to build a WCF service from an existing WSDL

      Unfortunately, that is not an option (at least not my favorite one). There
      are too many performance hit by using the ASMX, since IIS is involved. We
      are developing a data center application and require processing large amout
      of data via web services. If we cannot use WCF, we will have to dump .Net
      and switch to C++ (too bad).

      Thanks.
      Hao

      "Spam Catcher" <spamhoneypot@r ogers.comwrote in message
      news:Xns99AE863 2148C6usenethon eypotrogers@127 .0.0.1...
      "Hao" <Hao@newsgroup. nospamwrote in
      news:#s2yN5S#HH A.748@TK2MSFTNG P04.phx.gbl:
      >
      >I have an existing ASMX web service produced WSDL. I am trying to
      >upgrade the ASMX to WCF. The client side applications are already
      >deployed on customers sites. We are definitely not able to change the
      >WSDL in any way. Therefore I am thinking maybe the right approprach is
      >to start a WCF service from an existing WSDL.
      >What are the steps then?
      >
      I would stick with ASMX.

      Comment

      • Spam Catcher

        #4
        Re: How to build a WCF service from an existing WSDL

        "Hao" <Hao@newsgroup. nospamwrote in
        news:#MFqUJW#HH A.2752@TK2MSFTN GP06.phx.gbl:
        Unfortunately, that is not an option (at least not my favorite one).
        There are too many performance hit by using the ASMX, since IIS is
        involved.
        What sort of performance hit are you experiencing? Are you doing all the
        processing on the web server? Also web services are inherently slower
        due to the the need to serialize, transmit, receive, deserialize.

        You may want to adopt a tiered approach in which you process the data
        with a back end service. The web service is merely the front-end to the
        service.

        Or are you having trouble transmitting large amounts of data? In that
        case you should be looking into MTOM - it's part of Microsoft's WSE
        pack.
        We are developing a data center application and require
        processing large amout of data via web services. If we cannot use WCF,
        we will have to dump .Net and switch to C++ (too bad).
        How will WCF help you? Microsoft recommends hosting WCF in IIS if you
        want redundancy and load balacing.

        ServiceHost (self-hosting) WCF is not recommended for high volume.
        ServiceHost is only good if you need to maintain state or want the
        application to be standalone.

        Here is a good article describing WCF's hosting options:



        BTW, if you can host in IIS 7.0, you can host non-HTTP transports as
        well.

        But in in general, I think you have an issue with your architecture...
        not necessarily the technology?

        Comment

        Working...