You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "Ignite TC Bot (JIRA)" <ji...@apache.org> on 2019/03/04 06:37:00 UTC

[jira] [Commented] (IGNITE-11384) Introduce an ability of services hot redeployment via DeploymentSpi

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

Ignite TC Bot commented on IGNITE-11384:
----------------------------------------

{panel:title=--&gt; Run :: All: No blockers found!|borderStyle=dashed|borderColor=#ccc|titleBGColor=#D6F7C1}{panel}
[TeamCity *--&gt; Run :: All* Results|https://ci.ignite.apache.org/viewLog.html?buildId=3226745&amp;buildTypeId=IgniteTests24Java8_RunAll]

> Introduce an ability of services hot redeployment via DeploymentSpi
> -------------------------------------------------------------------
>
>                 Key: IGNITE-11384
>                 URL: https://issues.apache.org/jira/browse/IGNITE-11384
>             Project: Ignite
>          Issue Type: Sub-task
>          Components: managed services
>            Reporter: Vyacheslav Daradur
>            Assignee: Vyacheslav Daradur
>            Priority: Major
>              Labels: iep-17
>             Fix For: 2.8
>
>
> We can integrate service processor with DeploymentSpi to introduce an opportunity of services hot redeployment. For this change, the service processor should try to get and use registered classloader registered for the service's class in DeploymentSpi.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)