OASIS ebXML Messaging Services TC

 View Only

[ebxml-msg] RE: [ebxml-dev] ebxml message Validation Error

  • 1.  [ebxml-msg] RE: [ebxml-dev] ebxml message Validation Error

    Posted 07-02-2002 18:34
     MHonArc v2.5.2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    ebxml-msg message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


    Subject: [ebxml-msg] RE: [ebxml-dev] ebxml message Validation Error


    Hi Jeong,
    
    Incidentally, there seems to be a workaround for the exception
    you are seeing, at least under xerces 2.0.2 (only thing I tried).
    Consider these features:
    
        /** Default namespaces support (true). */
        protected static final boolean DEFAULT_NAMESPACES = true;
    
        /** Default validation support (false). */
        protected static final boolean DEFAULT_VALIDATION = true;
    
        /** Default Schema validation support (false). */
        protected static final boolean DEFAULT_SCHEMA_VALIDATION = true;
    
        /** you can have the above features set if you need them...**/
    ==================================================================
    
        /** Default Schema full checking support (false). */
        protected static final boolean DEFAULT_SCHEMA_FULL_CHECKING = false;
    ===========================================================
    
    The last feature controls whether a check is made 
    on "unique attribution constraints". The doc says:
    "Enable full schema constraint checking, including checking 
    which may be time-consuming or memory intensive. Currently, 
    particle unique attribution constraint checking and 
    particle derivation resriction checking are controlled
    by this option."
    
    With the option, on I was able to reproduce your
    error with a message containing an acknowledgment.
    With the full-checking option false, the error goes away.
    
    I will copy the Messaging list. Eventually
    a schema change or errata warning may be warranted.