Let's assume that I wanted to do some logic in groovy expression when inserting data to database. I have following jdbc-endpoint query configuration:
For simpler example I omitted the actual logic by throwing an Exception intentionally.
When I call the endpoint, no Exception is thrown to Mule. Only null value is inserted in the database. I think it is very dangerous if an Exception is not thrown when evaluating an expression. Now corrupted data may be added to database.
I think the cause is in
The ScriptException is omitted brutally. Could the exception be propagated so I would sleep better at nights?
|Field||Original Value||New Value|
|Priority||To be reviewed [ 6 ]||Critical [ 2 ]|
|Assignee||Pablo Kraan [ pablo.kraan ]|
|Resolution||Fixed [ 1 ]|
|Fix Version/s||3.2.2 [ 11105 ]|
|Fix Version/s||3.1.4 [ 11079 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Workflow||Fixed Main Mule Workflow (after JIRA upgrade) [ 81242 ]||Main Mule Workflow v1.0 [ 140094 ]|
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|302d 12h 34m||1||Pablo Kraan||20/Jan/12 02:21 PM|