ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node
Date Fri, 06 May 2016 16:44:12 GMT

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

ASF GitHub Bot commented on IGNITE-3056:
----------------------------------------

GitHub user ashutakGG opened a pull request:

    https://github.com/apache/ignite/pull/696

    Ignite services with different class loaders (Ignite 3056)

    https://issues.apache.org/jira/browse/IGNITE-3056

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/gridgain/apache-ignite ignite-3056-service-master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/696.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #696
    
----
commit 74a9e72fe819d62d5435fd03341d1c15dc1c6d43
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-28T15:05:43Z

    ignite-3056: added test

commit 0f8d0afeb989ca10951f3b87a303a071e3bf9f7c
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-28T17:34:14Z

    ignite-3056: potential fix with broken backword compatibility

commit 18fdcfab482c8bd528a57d5d3d1cb3cf9e1d0a1c
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-29T11:04:24Z

    ignite-3056: revert fix

commit 14391782c36e857a438575bd819c72b4956ee378
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-29T11:10:10Z

    ignite-3056: clean up

commit 7eaad5fbca168cb32430d73f5dcd9e67030cee3e
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-29T15:13:35Z

    ignite-3056: test (no pass...)

commit a8f1df1f6ebbe2647ee6d3d04017efbfae3f0bb5
Author: ashutak <ashutak@gridgain.com>
Date:   2016-04-29T15:42:20Z

    ignite-3056: added test reproducible test

commit ac52be0038680708209400aefcaf80e458942069
Author: ashutak <ashutak@gridgain.com>
Date:   2016-05-06T09:37:46Z

    ignite-3056: test works

commit f52ecaa0f839c2404c6e8525ae0d5b8cc12cc04a
Author: ashutak <ashutak@gridgain.com>
Date:   2016-05-06T10:21:49Z

    ignite-3056: finished with 1 class loader tests

commit 05283c46e07d50194bf9f1b19bc1f1b5fe17a1d0
Author: ashutak <ashutak@gridgain.com>
Date:   2016-05-06T15:53:51Z

    ignite-3056: fixed and added tests

commit 45dd971b4878c440db3903626281868a0642e2af
Author: ashutak <ashutak@gridgain.com>
Date:   2016-05-06T16:42:35Z

    ignite-3056: rework tests

----


> Service implementation class is required even if it's not expected to be deployed on
current node
> -------------------------------------------------------------------------------------------------
>
>                 Key: IGNITE-3056
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3056
>             Project: Ignite
>          Issue Type: Bug
>          Components: managed services
>    Affects Versions: 1.5.0.final
>            Reporter: Valentin Kulichenko
>            Assignee: Artem Shutak
>              Labels: community, customer, important
>             Fix For: 1.6
>
>
> Currently the service instance is deserialized as part of {{GridServiceDeployment}} and
{{GridServiceAssignment}} classes. Need to check if it's possible to deserialize only node
filter first, and then deserialize the service itself only if needed. This will allow to use
cluster groups with services and deploy the classes accordingly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message