As part of the work done on KOGITO-4013, we identified that the process marshaller needs to be revisited in order to provide a better fit into Kogito. Some of the goals include:

• Removing the dependency to any v7 API
• Removing dependency to Drools API
• Removing non-process related data from the resulting binary.

Some of the strategies that the team needs to discuss is whether is will be a brand new implementation, maybe reconsidering protobuf 3 with JSON support ( https://developers.google.com/protocol-buffers/docs/proto3#json ) as some might find useful for persistence. Or simply fixing/adjusting what we currently have.

[NOTE]

• Removing the dependency to any v7 API
• Removing dependency to Drools API
• Removing non-process related data from the resulting binary.
• two formats json/protobu
• simplication object marsharller strategies
• unifications of mongo db with other persistance addons.
• bump to proto3
• simplification of format
• removed facts from ruleset (N/A anymore)
• async node removed
• process xml removed
• triggers removed (was not used anyway)
• removed protobuf-persistence-common (integrated in the module)
• simplification of object strategies (detected by ServiceLoader)