Jochen,
Did you miss the original posting and if so, do you have any input on this
possible issue?
Regards,
Jimisola
Jimisola Laursen wrote:
>
> Hi,
>
> I found a bug (limitation in the XMLRPC library when it comes to
> de-serializing Maps.
>
> API method is:
>
> setSomething(Map<Integer, String> something)
>
> However, when the map is de-serialized/reconstructred on the server-side
> the key is not an integer. It is instead a char array (i.e. char[]).
>
> That is,
>
> on client:
>
> key: Integer(11)
> value: String("somestring")
>
> becomes:
>
> key: char[2] {'1','1'}
> value: String("somestring")
>
> on server. Is this by design or is this a bug?
>
> I am using Java 1.5, so I understand if generics don't work but
> serialization/de-serialization shouldn't be affected by that or?
>
> Regards,
> Jimisola
>
>
>
--
View this message in context:
http://www.nabble.com/Possible-de-serialization-bug-tf2630162.html#a7434742
Sent from the Apache Xml-RPC - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
