MobileApplicationsCSM/unicorn — Issue #20: HessianKit Archiver doesn't receive the real value object
Author: southdesign
Created: 2011-11-22 22:40:53+00:00
State: open

We just found out that the object that is received on the server side is not really the value object we put in on the other side. It's acutally a NSMutableDictionary with the attributes as keys. The values are correct but there's no way we could find out the class or protocol of the object.

Workarounds would be to introduce a classname attribute in every value object, so we would know what to cast to or generate a general wrapper around the object to send, which is probably not even slightly the intend of the hessian protocol.

I'm firing up wireshark now to see if the classname is arriving at the receiving end at all. We have no documentation for the hessian kit at all, which pretty much sucks because we have to reengineer the archiver and unarchiver classes.

Anyone another clue? How does the Java Server know which type ob object arrived? You have to pass him an interface, right?