[
https://issues.redhat.com/browse/DROOLS-5401?page=com.atlassian.jira.plug...
]
Toshiya Kobayashi updated DROOLS-5401:
--------------------------------------
Description:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to
non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException
only in unusual cases but still it's better to log and return rather than throwing
RuntimeException.
Btw, we can detect non-externalized lambda with option
"drools.check.nonExternalisedLambda" (DROOLS-5346).
was:
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to
non-externalized lambda. So it's better to log warn messages and return rather than
RuntimeException.
Btw, we can detect non-externalized lambda with option
"drools.check.nonExternalisedLambda" (DROOLS-5346).
Suppress RuntimeException in ExecModelLambdaPostProcessor
---------------------------------------------------------
Key: DROOLS-5401
URL:
https://issues.redhat.com/browse/DROOLS-5401
Project: Drools
Issue Type: Enhancement
Components: executable model
Affects Versions: 7.38.0.Final
Reporter: Toshiya Kobayashi
Assignee: Toshiya Kobayashi
Priority: Minor
When we hit an issue in ExecModelLambdaPostProcessor, we want to silently fall back to
non-externalized lambda. Currently ExecModelLambdaPostProcessor throws RuntimeException
only in unusual cases but still it's better to log and return rather than throwing
RuntimeException.
Btw, we can detect non-externalized lambda with option
"drools.check.nonExternalisedLambda" (DROOLS-5346).
--
This message was sent by Atlassian Jira
(v7.13.8#713008)