Anonymous | Login | Signup for a new account | 12-17-2024 08:31 PST |
Main | My View | View Issues | Change Log | Docs |
Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||
0002298 | [Resin] | minor | always | 01-08-08 08:33 | 01-08-08 13:22 | ||||
Reporter | sam | View Status | public | ||||||
Assigned To | ferg | ||||||||
Priority | normal | Resolution | fixed | ||||||
Status | closed | Product Version | 3.1.5 | ||||||
Summary | 0002298: burlap Locale deserialisation | ||||||||
Description |
(rep by M Vandamme) We have encountered a bug with Locale deserialisation. When a locale is passed to the server, it is passed as a LocaleHandle. The server tries to deserialise this type, but this fails. After this, the server tries to put the sent data into a locale object, while the LocaleHandle should construct the locale object. After some debugging, the problem was traced to the BurlapInput class, in the readObject method. Following code is present in the class ... if (cl != reader.getType() && cl.isAssignableFrom(reader.getType())) return reader.readMap(this); reader = _serializerFactory.getDeserializer(cl); return reader.readMap(this); cl = java.util.Locale reader.getType() = LocaleHandle The isAssignableFrom returns false, so the readMap is executed on the wrong reader, the one that is fetched for deserializing cl. |
||||||||
Additional Information | |||||||||
Attached Files | |||||||||
|
Mantis 1.0.0rc3[^]
Copyright © 2000 - 2005 Mantis Group
29 total queries executed. 26 unique queries executed. |