Bug 496155 - Crashing java services called throught AQL are not logged
Summary: Crashing java services called throught AQL are not logged
Status: CLOSED DUPLICATE of bug 495036
Alias: None
Product: Sirius
Classification: Modeling
Component: Properties (show other bugs)
Version: 4.0.0   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-06-15 04:46 EDT by Arthur Daussy CLA
Modified: 2016-06-24 05:03 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arthur Daussy CLA 2016-06-15 04:46:18 EDT
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.
Comment 1 Pierre-Charles David CLA 2016-06-22 04:18:33 EDT
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 ***