Vyacheslav Daradur created IGNITE-11539:
---
Summary: Document services hot redeployment via DeploymentSpi
Key: IGNITE-11539
URL: https://issues.apache.org/jira/browse/IGNITE-11539
Project: Ignite
Vyacheslav Daradur created IGNITE-11384:
---
Summary: Introduce an opportunity of services hot redeployment via
DeploymentSpi
Key: IGNITE-11384
URL: https://issues.apache.org/jira/browse/IGNITE-11384
Denis,
I've just prepared PR [1] with a possible implementation that covers
p.1 from your list.
Please, have a look at it. Pay attention to the test, it demonstrates
manual services hot-redeployment via DeploymentSpi.
Is that what you mean?
[1] https://github.com/apache/ignite/pull/6060
;
> > Sounds like a good plan. Does it mean that a user will have to
> > register a classloader for service's class explicitly in case of using
> > the feature?
> >
> > On Mon, Feb 4, 2019 at 4:38 PM Denis Mekhanikov
> wrote:
> > >
> > > I
mples for a DeploymentSPI usage.
>> As far as I can see, there is no such examples in our codebase for now.
>> Is it correct? If so, I will create a ticket to create such examples.
>>
>> В Вт, 05/02/2019 в 01:08 +0300, Vyacheslav Daradur пишет:
>> > Denis, thank you for
>
> > I'd like to start a dedicated thread for discussion of the design of
> > services hot redeployment. The previous service design discussion can be
> > found in the following thread: [1]
> >
> > Currently adding a new service or implementation change of an exis
gt; I'd like to start a dedicated thread for discussion of the design of
> services hot redeployment. The previous service design discussion can be
> found in the following thread: [1]
>
> Currently adding a new service or implementation change of an existing one
> requires restarting
Igniters,
I'd like to start a dedicated thread for discussion of the design of
services hot redeployment. The previous service design discussion can be
found in the following thread: [1]
Currently adding a new service or implementation change of an existing one
requires restarting the hosting
