Community
Participate
Working Groups
If a Java service (called throught AQL) crashes the error is logged. Here is my use case: 1. Creates a property view with a widget 'A'. 2. In the widget 'A' create a widget action that calls a java service name getAllX (throught a ChangeContext item) 3. In the implementation of getAllX, make a modification in the models (for example add a element in a existing EList) in order to create a "Can not modify a resource without creating a transaction" exception. 4. Execute This error is never log. Instead the framework fails silently and does nothing.
Marking as duplicate of #495036, which is about more robust handling of exceptions and errors that can occur during service invocation (or expression evaluation in general). *** This bug has been marked as a duplicate of bug 495036 ***