On Jun 11, 2007, at 11:42 AM, Jean-Francois Poilpret wrote:
I would like to re-open this old thread because I have just been
bitten by
this kind of problem.
Before, I was using Hessian 3.0.13 but I recently upgraded to 3.1.1.
I saw immediately that all classes for my transferred objects had to
implement Serializable (which they didn't do before). No problem
with that,
I made them all implement Serializable.
I've just added this as a bug report at http://bugs.caucho.com/
view.php?id=1796
-- Scott
However, I have just got a problem that I cannot solve: a library is
throwing an exception that includes a non-serializable member (this
library
is apache derby 10.2.2.0, the exception is derby own SqlException, the
member is Sqlca). Since I embed this exception in my own exceptions
transferred through hessian, I am stuck because I cannot change
derby source
code!
For info, this bug in derby has been fixed on SVN but not in any
official
release. Since I don't want to impose users to build derby from the
source,
I have to find another way to workaround that issue.
What I would really appreciate is that the new JavaSerializer
behavior (ie
checking that transferred objects implement Serializable) is an
option that
can be set/unset in some way.
Else the only other work-around that I can think of (very ugly) is
copy the
current hessian JavaSerializer to my own one, remove the first
lines of the
constructor, and replace the hessian one by my own version (this
without
touching hessian jars because I don't want my users to use exclusively
"official" OSS libs releases.
_______________________________________________
hessian-interest mailing list
[email protected]
http://maillist.caucho.com/mailman/listinfo/hessian-interest
