Nirva Application Platform

Hello,

As described in the subject, the problem is linked to Nirva exception propagation in Java procedures.
The Java file joined to the issue contains 4 methods.
main : method calling the 2 other methods as Java procedures to display the Nirva error caught
wrongError : method to illustrate the problem.
goodError : method to illustrate when it is ok.
wrongErrorNotWorkaroundable : method to illustrate that it may be impossible to reorganize code.

Description when problem occurs (wrongError method):
The code sets the Nirva error via SetErrorEx method.
It then launches a nirva Command, with NV_NO_ERROR and NV_KEEP_ERROR flags to YES.
A debug message is logged. It shows the correct error.
But in the main procedure, the error caught is not the logged error.

In the wrongError method, several workarounds exist : moving up Nirva command or resetting SetErrorEx with ("", "", -1, "") parameters right before return statement.
But in the wrongErrorNotWorkaroundable method the executed code is the same but the workarounds can not be applied.
The only solution found is to set a SetErrorEx with ("", "", -1, "") parameters in the finally statement. But it is executed also when no errors occur and I do not know if I can rely on this command not to send an error to Nirva.

I also noted (see main method) that returning 0 to the procedure does not mean the procedure won't throw a Nirva exception if SetErrorEx has been set with ("", "", -1, "") parameters and a previous error exists. Is it the wanted behaviour ?

Note : tested on Linux plateform, not the others, but it should not be related.