[
https://issues.apache.org/jira/browse/IGNITE-17022?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pavel Pereslegin resolved IGNITE-17022.
---------------------------------------
Release Note: Added the ability to intercept calls to service methods.
Resolution: Done
> Implement interceptors for Ignite Services
> ------------------------------------------
>
> Key: IGNITE-17022
> URL: https://issues.apache.org/jira/browse/IGNITE-17022
> Project: Ignite
> Issue Type: Improvement
> Reporter: Maxim Muzafarov
> Assignee: Pavel Pereslegin
> Priority: Major
> Labels: iep-79, important, ise
> Fix For: 2.14
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currenlty, Ignite Services has a lack of support execution a custom
> middleware process before and after a service execution. This leads to a lot
> of boilerplate code.
> The IEP-79 describes a draft API of such a feature implementation:
> https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=191334119
> However, we still need to consider additional crucial points of such API:
> - sync or async listeners/interceptors execution (some of processes may
> require to set and clear threadlocals);
> - an exception in the inteceptrod should or should not interrupt a service
> execution;
> - {{context}} may need to be accessible inside interceptors and services;
> Also we need to add description about what kind of the {{guarantees}} are
> provided by Ignite server node during a service execution. It may be
> necessary to consider the service-per-thread execution logic.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
