Aaron Mulder wrote:
> 
>         Hmmm... disturbing.  I've never seen a JDBC driver try to
> deserialize internally to reply to getObject.  I've only seen it return a
> raw byte array from getObject if it didn't have anything more appropriate.
> Hmph.  I'm not sure there's an answer to this one.

I guess this is another point for "setParameter and getResultObject
should be DB-specific"...


>         The correct ClassLoader, for what it's worth, is
> Thread.currentThread().getContextClasLoader() which seems to be used by
> RMI but not a general ObjectInputStream.  So one solution would be for the
> Hypersonic folks to use that when they deserialize.  Another would be
> for getObject to return a byte array, as I've seen it do before (though
> I can't remember whether it was Hypersonic or InstantDB).  I'm a little
> uncomfortable about never trying getObject if we can't figure out what to
> call, since I'm not sure getBytes would return something coherent if there
> was actually a valid Object in the result set.

I agree.
I will test Rickard's idea (MarshalledObject) right away.


Sebastien

Reply via email to