IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
  • 1.  [ISC.0124.9002] Document to XSD error

    Posted Wed August 07, 2013 02:43 PM

    Hello,

    I’m trying to do the following procedure:
    Create a WSD Consumer
    Create a WSD Provider from that consumer and i’m having the error:

    [ISC.0081.9164] Exception occurred during generation of WSDL for service Wiz_WSD:
    [ISC.0124.9002] Document to XSD error: Document tns:QuestionResponse cannot be represented in XML Schema.
    This document contains a *body field constrained by a simple type and fields that would be represented as elements in the XSD. XSD could describe this document if the simple type constraint was removed or the non-attribute fields were deleted

    The doctype is in the image as example.

    My questions are:
    Is there a way to go around this error without changing doctypes?
    Why does this error occurs?
    Is there a way to import the doctypes with the field *body without constraints?

    Thanks
    Mauro Ribeiro


    #webMethods
    #API-Management
    #soa


  • 2.  RE: [ISC.0124.9002] Document to XSD error

    Posted Fri August 09, 2013 03:14 PM

    character:* can’t be used as leading character in any XML name, so you won’t be able to use
    *body

    check the XML spec here:
    http://www.w3.org/TR/2004/REC-xml-20040204/


    #API-Management
    #webMethods
    #soa


  • 3.  RE: [ISC.0124.9002] Document to XSD error

    Posted Tue August 13, 2013 11:41 AM

    When I import with developer it works, it creates a doctype with this elements:
    *body
    @desc
    but when I import with designer 8 it doesnt work and creates a doctype with this elements:
    *body
    @desc
    *doctype


    #API-Management
    #webMethods
    #soa


  • 4.  RE: [ISC.0124.9002] Document to XSD error

    Posted Tue August 13, 2013 12:05 PM

    When you generate a WM doc definition, if the element has a attribute, WM will generate the element with two sub-fields:
    *body
    @theAttribute

    This make it unusable in WS descriptor directly.

    Actually, when you create WS, you don’t want to embed the whole xml structure as part of the WS definition. You can simply use one parameter, for example: PayloadDocument, make it a String.
    then, you do the parsing, processing in separate services. SO you won’t have this issue.
    This is also a better practice, avoid changing of WS when you need to modify your XML schema.


    #API-Management
    #soa
    #webMethods