[ 
https://issues.apache.org/jira/browse/IGNITE-16234?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Roman Puchkovskiy updated IGNITE-16234:
---------------------------------------
    Description: 
User Object Serialization (IGNITE-15944) might be used to serialize compute 
tasks and other components supplied by a user, sent via network, unmarshalled 
and executed on Ignite nodes.

Such serialized components may need access to Ignite resources. It makes sense 
to inject them to fields annotated with a special-purpose annotation (like it 
was it Ignite 2).

An example of such annotation in Ignite 2 is @TaskSessionResource.

  was:
[User Object Serialization](IGNITE-15944) might be used to serialize compute 
tasks and other components supplied by a user, sent via network, unmarshalled 
and executed on Ignite nodes.

Such serialized components may need access to Ignite resources. It makes sense 
to inject them to fields annotated with a special-purpose annotation (like it 
was it Ignite 2).


> Implement injection of Ignite resources on unmarshalling
> --------------------------------------------------------
>
>                 Key: IGNITE-16234
>                 URL: https://issues.apache.org/jira/browse/IGNITE-16234
>             Project: Ignite
>          Issue Type: Improvement
>          Components: networking
>            Reporter: Roman Puchkovskiy
>            Assignee: Roman Puchkovskiy
>            Priority: Major
>              Labels: ignite-3
>             Fix For: 3.0.0-alpha4
>
>
> User Object Serialization (IGNITE-15944) might be used to serialize compute 
> tasks and other components supplied by a user, sent via network, unmarshalled 
> and executed on Ignite nodes.
> Such serialized components may need access to Ignite resources. It makes 
> sense to inject them to fields annotated with a special-purpose annotation 
> (like it was it Ignite 2).
> An example of such annotation in Ignite 2 is @TaskSessionResource.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to