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 Wed, 11 May 2016 13:26:12 GMT

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

ASF GitHub Bot commented on IGNITE-3056:

GitHub user ashutakGG opened a pull request:


    Ignite services with different class loaders (ignite 3056)

    New PR for https://issues.apache.org/jira/browse/IGNITE-3056. Branch based on ignite-1.6.0

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

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

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


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

    This closes #700
commit e52706ce12428647467fb192560bc0df72cf95ee
Author: ashutak <ashutak@gridgain.com>
Date:   2016-05-11T13:21:41Z

    ignite-3056: implemented


> 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

View raw message