ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ihor Parashynets (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-1264) Resource SPI
Date Thu, 11 May 2017 10:15:04 GMT

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

Ihor Parashynets commented on IGNITE-1264:
------------------------------------------

hi all

is there a plan to move on this topic?

Thanks...

> Resource SPI
> ------------
>
>                 Key: IGNITE-1264
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1264
>             Project: Ignite
>          Issue Type: Improvement
>          Components: general
>            Reporter: Andrey Kornev
>
> As a user I'd like to be able to customize how resource injection is done by Ignite:
for example, I'd like to be able to process any custom annotations on my application's class
after its deserialization on a remote node.
> Ideally, Ignite should expose an SPI that would be delegated to at specific points of
the dependency injection logic (as currently implemented in the GridResourceProcessor class).
> Once implemented, this feature would allow to make the injector support pluggable: Spring,
Guice, Dagger, whatever... Ultimately it'd be great to replace all injection-related Ignite
annotations by the standard javax.inject API.
> For references, here's the nabble thread: http://apache-ignite-developers.2346864.n4.nabble.com/Resource-SPI-proposal-td2318.html



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message