[
https://issues.apache.org/jira/browse/IGNITE-14402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308642#comment-17308642
]
Aleksey Plekhanov commented on IGNITE-14402:
--------------------------------------------
{quote}Do NOT implement JCache, but use CacheEntryListener interface family and
return null from CacheEntryEvent.getSource.
{quote}
We can't do this, the {{source}} is required to be not null (see
{{EventObject}} constructor). Instead, we can build some private ClientCache to
JCache adapter and use it as a {{source}}.
Currently, in my draft, it's implemented as "create interfaces from scratch",
and it looks weird. I think the third or fourth option is more suitable for
this task.
There was a discussion about thin client API on dev list
[http://apache-ignite-developers.2346864.n4.nabble.com/DISCUSSION-Consistency-across-java-thin-thick-APIs-td48914.html],
but unfortunately without any final decision.
> Java Thin: Continuous Query
> ---------------------------
>
> Key: IGNITE-14402
> URL: https://issues.apache.org/jira/browse/IGNITE-14402
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-50
> Fix For: 2.11
>
>
> Implement Continuous Query API in Java Thin Client.
> See .NET Thin Client as a reference: IGNITE-13148
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
