Hi,
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.
What would be the best way to fix this problem?
**** DISCLAIMER ****
<A HREF="http://www.tvh.be/newen/pages/emaildisclaimer.html";>
http://www.tvh.be/newen/pages/emaildisclaimer.html </A>
"This message is delivered to all addressees subject to the conditions
set forth in the attached disclaimer, which is an integral part of this
message."
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
