CapableObjects Forums SupportForum ModelChecksumPrecondition

This topic contains 3 replies, has 2 voices, and was last updated by  efim 2 weeks, 6 days ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #4769



    I have no idea what could it be:

    Der Formatierer hat beim Deserialisieren der Nachricht eine Ausnahme ausgelöst: Fehler beim Deserialisieren von Parameter Die InnerException-Nachricht war “Fehler in Zeile 1, Position 5946. Das Element “” enthält Daten eines Typs, der dem Namen “” zugeordnet ist. Dem Deserialisierungsprogramm ist kein Typ bekannt, der diesem Namen zugeordnet ist. Verwenden Sie ggf. einen DataContractResolver, oder fügen Sie den entsprechenden Typ für “ModelChecksumPrecondition” der Liste der bekannten Typen hinzu. Verwenden Sie dazu z. B. das Attribut “KnownTypeAttribute”, oder fügen Sie den Typ der an DataContractSerializer übergebenen Liste von bekannten Typen hinzu.”

    I have added ModelChecksumPrecondition to known types like this:
    but it did not help




    Hi Efim,

      [KnownType (typeof(OptimisticLockingPrecondition))]
      public abstract class UpdatePrecondition { }

    The Update Precondition has been extended with an option. It is a precondition ModelChecksumPrecondition that can be made to enforce the same model on the client as in the persistence server. The condition was introduced after clarification that some (all) data inconsistencies was created by writes from clients with other model version.

    The OptimisticLockingPrecondition now inherits from ModelChecksumPrecondition

    Is your persistence server compiled with a too old MDriven Version?


    The strange thing is that I am working a while with this version, but this error came for a pair of days after I extended model class with 2 attributes.




    I could recover it by going backwards to earlier versions and step-by-step reconstruction my changes. No update to later MDriven versions was needed.
    No idea what has happened

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.

Comments are closed.