For information.
I implemented a workaround and opened a pull request for this issue:
https://github.com/droolsjbpm/drools/pull/176
The implemented workaround is the lowest impact workaround I could think of:
Preload the stream into memory before unmarshalling, and ProtoBuf will not
enforce the m
Pull request submitted at github:
https://github.com/droolsjbpm/drools/pull/170
It's targetting 5.5.x
Fingers crossed!
--
View this message in context:
http://drools.46999.n3.nabble.com/Why-are-indented-keywords-in-template-causing-NPE-or-DecisionTableParseException-tp4021193p4021289.html
Drools 5.5.0
Indenting the "template header" or "rule" keywords in a template file will
cause exceptions on expansion. I believe it might be related to this old
JIRA issue: https://issues.jboss.org/browse/JBRULES-2786
"DecisionTableParseException" and "NullPointerException" are thrown. See
exampl
Does this mean that the JPA persistence has to write out the entire
knowledgesession every time a new fact is inserted?
I.e. If I have 279 facts, when I insert fact #280, the JPA will write out
all 280 facts. It has no way of just writing the delta between 279 and 280?
Thanks
--
View this mess
Are there any disadvantages to using the Marshaller instead of JPA for
persistence?
We are running Drools as an embedded service, and we would favor the
Marshaller because we don't want to handle the persisting of the session id
between system reboots. We're currently not using JPA in our system,
