Well, I'm not sure what's the best approach, but your suggestion would
perhaps add more verbosity and so needs to have a reason.
Exceptions are not always necessarily a "bad" thing, they're just a
language feature to indicate a different path of execution, so
bubbling an exception to stop a
Hello !
While we are working on Groovy migration at Nereide, we figured out that
using ‘run service’ DSL method instead of returning the errorMap, a
‘ExecutionServiceException’ is thrown :
if (ServiceUtil.isError(result)) {
throw new