Using JDeveloper 188.8.131.52.0 a bounded task-flow can be dropped on a page as a "Dynamic Region",
which will typically result in a taskFlow executable binding with a taskFlowId EL expression referring to a method like
Such getDynamicTaskFlowId() method can evolve in more complex code (where an exception can be thrown).
If such method would throw an exception, it seems to be eaten by the framework.
Please consider the example application created using JDeveloper 184.108.40.206.3.0
Its getDynamicTaskFlowId() method explicitly throws an exception by calling the getDynamicTaskFlowIdThrowingException() method.
Running the "trySomeBTF" view activity in the unbounded task-flow will result in an empty page.
Nothing about the exception is shown on the page.
Nothing about the exception is shown on the Log panel in JDeveloper.
So, the exception seems to be "eaten" by the framework.
Can the eaten exception behavour described above be reproduced?
Is the eaten exception behavour described above intended behaviour?