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
Expand all | Collapse all

7.1.3 Integration Server doesnt recognize patterns in XSD

  • 1.  7.1.3 Integration Server doesnt recognize patterns in XSD

    Posted Tue November 01, 2011 07:08 PM

    Hi All

    We have an XSD which contains the following pattern or restriction for one of the string fileds ([1-9]|1[0-1]).

    I am trying to publish the document which is created from the above XSD to the broker ,but whenever the value of the field is greater than 9,then the publish service is failing with the below mentioned error

    pathName=/Body/CarNo
    errorCode=DT-012 errorMessage=[ISC.0082.9469] Value does not match
    pattern(s)

    I suspect webMethods is not able to read or understand the second condition in the pattern and hence its always failing when the value is greater than 9.

    The same expression works successfully in java so there don’t seem to be
    any issue with the expression as such.

    Have any of faced this issue and please suggest what fix used to resolve this issue.

    Please find our current patch level.

    IS_7.1.3_Core_Fix13

    Thanks in advance

    Mani


    #Flow-and-Java-services
    #webMethods
    #Integration-Server-and-ESB


  • 2.  RE: 7.1.3 Integration Server doesnt recognize patterns in XSD

    Posted Wed November 02, 2011 11:48 PM

    Your regex fails in xml schema mode in regex buddy.

    Java regex and xml regex have different syntax.

    This might work: (1[0-1])|([1-9])


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods


  • 3.  RE: 7.1.3 Integration Server doesnt recognize patterns in XSD

    Posted Sun November 06, 2011 12:46 PM

    Also important to note webMethods Broker is not Java based, it’s C. It has a Java API but the core is C.

    As a design note, best to leave out of the XML schema the enforcement patterns and leave that up to the business rules. Interop issues almost always occur the more complex the XML schema becomes. It can also potentially hamper reuse.


    #Integration-Server-and-ESB
    #Flow-and-Java-services
    #webMethods