[
https://issues.apache.org/jira/browse/THRIFT-1964?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13654582#comment-13654582
]
Jens Geyer edited comment on THRIFT-1964 at 5/10/13 4:44 PM:
-------------------------------------------------------------
-I'm about to prepare a patch ...- here it is.
The issets are now ignored in all serialization scenarios, they are restored
correctly during deserialization. Tested with C# 2010:
- on Win8 (the XmlSerializer testcase above) using -gen csharp with no flags
- on WinPhone7 (SILVERLIGHT defined) using -gen csharp:serial,asyncctp
was (Author: jensg):
I'm about to prepare a patch, just in case ...
> 'Isset' will cause xmlserializer crashed.
> -----------------------------------------
>
> Key: THRIFT-1964
> URL: https://issues.apache.org/jira/browse/THRIFT-1964
> Project: Thrift
> Issue Type: Bug
> Components: C# - Compiler
> Affects Versions: 0.9
> Environment: .net framework 3.5
> Reporter: xq.gzh
> Labels: Isset
> Attachments: a.thrift, Program.cs, ReproduceTheIssue.zip,
> THRIFT-1964_Isset_causes_xmlserializer_exeption.patch
>
> Original Estimate: 8h
> Remaining Estimate: 8h
>
> same class name 'Isset' in user defined class will cause xmlserializer
> crashed.
> below is the sample thrift:
> struct A {
> 1: string x;
> }
> struct B {
> 1: string y;
> }
> struct C {
> 1:A a
> 2:B b
> }
> generate code and try xmlserialize instance of class C. it crashed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
