[
https://issues.apache.org/jira/browse/IGNITE-14251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mikhail Petrov updated IGNITE-14251:
------------------------------------
Description:
It's proposed to change names of the following proxy classes to make them more
consistent:
IgniteProxyImpl -> IgniteNodeProxy
ClosableIgniteProxyImpl -> ClosableIgniteNodeProxy
IgniteCacheClientProxy -> IgniteClientCacheProxy
It's also proposed to reuse ignite-spring-data-commons module in
ignite-spring-tx-ext tests as ClientCacheProxy and IgniteCacheProxy duplicate
existing IgniteCacheProxy functionality.
was:
It's proposed to change names of the following proxy classes to make them more
consistent:
IgniteProxyImpl -> IgniteNodeProxy
ClosableIgniteProxyImpl -> ClosableIgniteNodeProxy
IgniteCacheClientProxy -> IgniteClientCacheProxu
It's also proposed to reuse ignite-spring-data-commons module in
ignite-spring-tx-ext tests as ClientCacheProxy and IgniteCacheProxy duplicate
existing IgniteCacheProxy functionality.
> Ignite extensions: refactor proxy classes names
> -----------------------------------------------
>
> Key: IGNITE-14251
> URL: https://issues.apache.org/jira/browse/IGNITE-14251
> Project: Ignite
> Issue Type: Improvement
> Reporter: Mikhail Petrov
> Assignee: Mikhail Petrov
> Priority: Minor
>
> It's proposed to change names of the following proxy classes to make them
> more consistent:
> IgniteProxyImpl -> IgniteNodeProxy
> ClosableIgniteProxyImpl -> ClosableIgniteNodeProxy
> IgniteCacheClientProxy -> IgniteClientCacheProxy
>
> It's also proposed to reuse ignite-spring-data-commons module in
> ignite-spring-tx-ext tests as ClientCacheProxy and IgniteCacheProxy duplicate
> existing IgniteCacheProxy functionality.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)