Uploaded image for project: 'JBoss BPMS Platform'
  1. JBoss BPMS Platform
  2. RHBPMS-1460

[GSS] (6.1.z) EventFactHandles are not deserialized correctly causing error "No enum constant org.drools.core.factmodel.traits.TraitTypeEnum.xxx"

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Critical Critical
    • None
    • 6.1.0
    • jBPM Core
    • None

      +++ This bug was initially created as a clone of Bug #1264525 +++

      The following code causes errors "No enum constant org.drools.core.factmodel.traits.TraitTypeEnum.xxx"

      XStream xstream = BatchExecutionHelper.newXStreamMarshaller();
      ...
      ExecutionResults results = (ExecutionResults) xstream.fromXML(responseXml);

      The root cause is explained in the jira https://issues.jboss.org/browse/DROOLS-924
      "EventFactHandle overrides DefaultFactHandle's toExternalForm(), but it is not happening the same for the createFromExternalFormat() method. Moreover no code takes care of the 1st argument (the format version) of the serialized format so when deserializing it always instance a DefaultFactHandle even when it was serialized an event."

      — Additional comment from Mario Fusco on 2015-09-18 12:47:14 EDT —

      Fixed by https://github.com/droolsjbpm/drools/commit/59d791076204d28ed370bf83b7f21e9864b0a701 and https://github.com/droolsjbpm/jbpm/commit/c6fd866c5

      — Additional comment from JBoss Product and Program Management on 2015-09-18 12:50:08 EDT —

      Since this issue was entered in Red Hat Bugzilla, the release flag has been
      set to ? to ensure that it is properly evaluated for this release.

              mfusco@redhat.com Mario Fusco
              rhn-support-ghu Gary Hu
              Tomáš Livora Tomáš Livora (Inactive)
              Tomáš Livora Tomáš Livora (Inactive)
              Edson Tirelli, Karel Suta, Kris Verlaenen, Lukáš Petrovický (Inactive), Mario Fusco, Radovan Synek (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: