#13 WSDK: code gen fails for ExchangeService

closed
dmccrae
None
5
2009-07-09
2009-03-05
dmccrae
No

The attached service definition (for Microsoft Exchange web services)
fails to generate-wsdl-code. There are several problems.

* needs explicit schemaLocation for 'xml' namespace
* fails to resolve groups (all containing choice)
* choice elements fall back to 'any'
* complex types derived by restriction fall back to 'any'
* derived complex types fail when base is 'any' because of fallback
* unions produce duplicate definitions

WSDK is intended to "fall back" to use any/XDMElement in such cases,
but it is not working in this case, because of dependencies between
the types. If it did work, so many of the types would be returned as
XML, that it would be difficult to use the generated service package.

Discussion

  • dmccrae
    dmccrae
    2009-03-05

    ExchangeService definitions

     
    Attachments
  • dmccrae
    dmccrae
    2009-03-20

    Progress report:
    * unions problem (simple) has been fixed
    * representing complex types derived by restriction is feasible (not yet done)
    ** this should be sufficient for data transfer
    ** would not enforce restrictions
    * problem with groups is consequence of choice fallback
    ** that is feature request #2475120

     
  • dmccrae
    dmccrae
    2009-07-09

    With WSDK 2.0, service package code for this service can be generated and compiled without error. The generated code no longer includes XDMElement fallbacks for choice or restriction elements

    It is necessary to supply an explicit schemaLocation for the 'xml' namespace.

    I'm marking this issue closed, because the problems preventing compilation of the service package have been resolved. However, the service package has not been tested with a MicrosoftExchange server, and the schema uses many advanced problems, so it is possible that there might be further runtime problems.

     
  • dmccrae
    dmccrae
    2009-07-09

    • status: open --> closed