[
https://issues.apache.org/jira/browse/IGNITE-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15017741#comment-15017741
]
Pavel Tupitsyn commented on IGNITE-1964:
-----------------------------------------
Test scenario:
* register enum type in .NET
* register Java enum with the same name via configuration
* put an object to cache with a field of that enum type
* in Java task get cache value as binary and check that we can deserialize that
field
> .NET: Write enum type ID if possible.
> -------------------------------------
>
> Key: IGNITE-1964
> URL: https://issues.apache.org/jira/browse/IGNITE-1964
> Project: Ignite
> Issue Type: Sub-task
> Components: interop
> Affects Versions: ignite-1.4
> Reporter: Vladimir Ozerov
> Assignee: Pavel Tupitsyn
> Priority: Critical
> Fix For: 1.5
>
>
> Currently we always write -1 as enum type ID in .NET. We made this for two
> reasons:
> 1) .NET has fair generics and always has necessary type info to perform
> deserialization.
> 2) We do not have dynamic portable type register as in Java yet.
> However, this approach make it impossible to interoperate with Java when
> context cannot be inferred. E.g. in queries.
> Full solution:
> 1) Implement dynamic types register.
> 2) Always pass Enum type ID.
> Solution require in scope of this ticket due to tight release schedule:
> 1) Pass enum type ID when possible, i.e. when enum is restered as portable
> type explicitly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
