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.  processContents for ANY element

    Posted Tue March 19, 2002 05:19 PM

    How options of processContents for an ANY element works ?

    I need to use an ANY element to store ANY content like XML, XHTML. The following XML document is an example:

    <?xml version="1.0" encoding="iso-8859-1" ?>

    simples

    Hi Peter, how are you?
    I?m fine.

    simples

    If I define a Schema with processContents = “skip”, in ANY element I can store it, but, what is the options Skip,Lax and Strict ?

    I use the following schema:

    <?xml version = "1.0" encoding = "UTF-8"?>
    <xs:schema xmlns:xs = “XML Schema” xmlns:tsd = “http://namespaces.softwareag.com/tamino/TaminoSchemaDefinition”>
    xs:annotation
    xs:appinfo
    <tsd:schemaInfo name = “Schema_ANY”>
    <tsd:collection name = “Collection_ANY”></tsd:collection>
    <tsd:doctype name = “DocANY”>
    tsd:logical
    tsd:contentclosed</tsd:content>
    </tsd:logical>
    </tsd:doctype>
    </tsd:schemaInfo>
    </xs:appinfo>
    </xs:annotation>
    <xs:element name = “DocANY”>
    xs:complexType
    xs:sequence
    <xs:element name = “SIMPLE1” type = “xs:string”></xs:element>
    <xs:any processContents = “skip”></xs:any>
    <xs:element name = “SIMPLE2” type = “xs:string”></xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>


    #Tamino
    #webMethods
    #API-Management


  • 2.  RE: processContents for ANY element

    Posted Wed March 20, 2002 11:02 AM

    For processContent attribute:
    “skip” means the content is not validated.
    “strict” means the content is validated. If there isn’t schema information for the content an error is flagged.
    “lax” means the content should be validated but if there is no schema information available no errors are flagged.

    Hope this helps.


    #Tamino
    #webMethods
    #API-Management


  • 3.  RE: processContents for ANY element

    Posted Wed March 20, 2002 11:30 AM

    Here is a short explanation:

    strict
    There must be a top-level declaration for the item available, or the item must have an xsi:type, and the item must be


    #Tamino
    #API-Management
    #webMethods


  • 4.  RE: processContents for ANY element

    Posted Wed January 21, 2004 05:59 PM

    Is xsi:type attribute supported by Tamino ?


    #webMethods
    #API-Management
    #Tamino


  • 5.  RE: processContents for ANY element

    Posted Thu January 22, 2004 11:36 AM

    Hi Jerome

    Tamino 4.1.4 will reject any document containing xsi:type by default.
    If you need to allow them (without actually processing them!) urgently:
    there is a workaround available since the September 2003 update kit
    which can be obtained from Tamino support.

    The next version of Tamino is able to validate vs. the type referenced
    by an xsi:type attribute without checking the additional constraints
    on the type hierarchy.

    Best regards
    Uli


    #API-Management
    #Tamino
    #webMethods


  • 6.  RE: processContents for ANY element

    Posted Thu January 22, 2004 01:46 PM

    Hi Ulrich,

    thank you very much for your answer. You mean that Tamino 4.2 will be able to validate xsi:type elements.

    I wonder if Tamino will manage efficient indexes if the referenced type is a complex type with declared indexed elements.

    best regards

    [This message was edited by Jerome Marc on 22 January 2004 at 13:24.]


    #Tamino
    #webMethods
    #API-Management