Clovertech

WSDL Cloverleaf and .NET

› Clovertech Forums › Read Only Archives › Cloverleaf › Cloverleaf › WSDL Cloverleaf and .NET

  • Creator
    Topic
  • September 19, 2008 at 6:37 am #50295
    Richard Hart
    Participant

      I’ve been working in a test environment with the Cloverleaf IB and Web Services.

      In theory, the content of a WSDL is written to standard, but it appears that there is a standard and a Microsoft standard!

      I’ve created a (simple) Web Service with a WSDL that SOAP UI understands and works.

      Unfortunately, the developers are using .NET which cannot understand the WSDL!  It sees the XML schemas, but cannot import them without namespace issues.

      Has anyone else had similar problems?

      I’m assuming that the Cloverleaf WSDL tools adhere to the standard, is this so?

      Thanks.

    • Creator
      Topic
    Viewing 0 reply threads
    • Author
      Replies
      • September 23, 2008 at 4:56 am #65523
        Richard Hart
        Participant

          I downloaded some ‘WSI Compliance’ tools that plug into SOAP UI and have checked the WSDL; this has ‘proved’ that the WSDL was not fully compliant and had namespace issues!

          [SOAP UI worked and the Cloverleaf ‘compilation has no issues]

          The work around is to create a ‘heavily typed’ schema that manually includes any ‘imported’ schemas. Create the WSDL file as usual and then perform a manual ‘include’ in the wsdl:types section.

          ie

          for the types section …

             

                <schema xmlns="http://www.w3.org/2001/XMLSchema”&gt;

                   

               

             

          Replace the with the contents of the xsd, in this case ‘CanisSetGeocodingData.xsd’.

      • Author
        Replies
      Viewing 0 reply threads
      • The forum ‘Cloverleaf’ is closed to new topics and replies.