You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Artem Shutak (JIRA)" <ji...@apache.org> on 2016/01/15 15:28:39 UTC

[jira] [Commented] (IGNITE-2395) Binary marshaller: id mapper must be resolved according to configuration.

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

Artem Shutak commented on IGNITE-2395:
--------------------------------------

There is a *workaround*. The following BinaryConfiguration have to be used:
{code}
        BinaryConfiguration bCfg = new BinaryConfiguration();
        bCfg.setIdMapper(BinarySimpleNameIdMapper.defaultInstance());
        bCfg.setTypeConfigurations(Arrays.asList(new BinaryTypeConfiguration("org.my.Class")));
{code}

> Binary marshaller: id mapper must be resolved according to configuration.
> -------------------------------------------------------------------------
>
>                 Key: IGNITE-2395
>                 URL: https://issues.apache.org/jira/browse/IGNITE-2395
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Artem Shutak
>            Assignee: Artem Shutak
>            Priority: Critical
>             Fix For: 1.6
>
>
> The following scenario does not works
> - start node with BinaryMarshaller and set BinaryConfiguration with not-default BinaryIdMapper (see BinarySimpleNameIdMapper)
> - Execute the following code (it fails):
> {code}
>         BinaryObjectBuilder builder = builder("org.my.Class");
>         BinaryObject bo = builder.build();
>         assertEquals("class".hashCode(), bo.type().typeId());
> {code}



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