[ 
https://issues.apache.org/jira/browse/GEODE-10402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17603522#comment-17603522
 ] 

ASF subversion and git services commented on GEODE-10402:
---------------------------------------------------------

Commit 992703da07cf80c37cefc84dd409ba5b0e383dd0 in geode-native's branch 
refs/heads/develop from Mario Salazar de Torres
[ https://gitbox.apache.org/repos/asf?p=geode-native.git;h=992703da0 ]

GEODE-10402: Fix FunctionException handling (#981)

* GEODE-10402: Fix FunctionException handling

 - Fixed handling for FunctionException.
 - Added InternalFunctionInvocationTargetException and replaced
   GF_FUNCTION_EXCEPTION by
   GF_INTERNAL_FUNCTION_INVOCATION_TARGET_EXCEPTION, so function
   exceptions are properly handled.
 - Code modified to adapt to the above changes.

* GEODE-10402: Revision 1

 - Actually added handling for FunctionException exception in
   ThinClientRegion.
 - Removed InternalFunctionInvocationTargetException as part of the
   public API since this is part of the internal Java API.
 - Added a new IT to verify that FunctionExceptions thrown by the user
   are actually thrown in the native library as FunctionException's.

* GEODE-10402: Format code

* GEODE-10402: Revision 2

 - Fixed clang-tidy warnings.
 - Fixed format on one of the Java classes for testing.

> Fix FunctionException handling
> ------------------------------
>
>                 Key: GEODE-10402
>                 URL: https://issues.apache.org/jira/browse/GEODE-10402
>             Project: Geode
>          Issue Type: Bug
>          Components: native client
>            Reporter: Mario Salazar de Torres
>            Assignee: Mario Salazar de Torres
>            Priority: Major
>              Labels: needsTriage, pull-request-available
>
> *GIVEN* a ServerFunction throwing a FunctionException
> *WHEN* its executed
> *THEN* a CacheServerException is thrown rather FunctionException
> ----
> *Additional info.* FunctionException seems not to be handled, that's why the 
> default handling exception is thrown by the native API, CacheServerException



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to