You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Sergey Chugunov (Jira)" <ji...@apache.org> on 2022/04/13 11:49:00 UTC
[jira] [Created] (IGNITE-16846) Internal API modules cleanup
Sergey Chugunov created IGNITE-16846:
----------------------------------------
Summary: Internal API modules cleanup
Key: IGNITE-16846
URL: https://issues.apache.org/jira/browse/IGNITE-16846
Project: Ignite
Issue Type: Task
Components: networking
Reporter: Sergey Chugunov
Two modules containing internal APIs need refactoring and cleanup.
* *network-api* module contains classes and interfaces placed in public packages (without *internal* package in their full paths) that shouldn't be exposed to the end-user;
* *configration-api* module contains mix of classes, interfaces and annotations some of them are clearly internal and some of them are used in ignite-api module which is definitely public.
We should address it in the following way:
* in *network-api* module it is enough to rename packages and add *internal* package to the full path;
* in *configuration-api* we need to move code around: as we don't have embedded mode of server nodes user won't interact with Java configuration directly. Thus configuration schema classes can be moved from *ignite-api* module to modules where this configuration classes belong to. After that we could add *internal* package to full path of all classes in *configuration-api* module as well.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)