Hello Chris,
I've made some tests using the default converter and there should be some
trace in the logs.
When the converterService is not able to find a converter for an object (for
example, it does not implement the Serializable interface) there is a
warning trace ("Unable to find a converter for this object"), and when the
object contains attributes that doesn't implement Serializable, there is a
warning exception ("Exception while writing the message body.") and a
stacktrace of a java.io.NotSerializableException exception.
Could you precise your context? for example, the list of extensions, the
version of the framework?
Best regards,
Thierry Boileau
I'm just getting started with Restlets. I'll be building both the server-
> and client-sides of a system. I have just completed a basic unit test that
> tests from the client to get and validate data from the server - the unit
> test encapsulates both sides. As soon as I evolved my code to send a more
> complex class, rather than primitives, I started getting NPEs on the server
> side. I eventually determined this is due to the class I am sending not
> being serializable. However, no serialization exception was thrown on the
> client. The client silently substituted NULL for my object and sent it
> merrily on its way.
>
> My question is: Is this by design? If yes, can someone explain the intent?
> Because from the perspective of this first-time user, this is an
> unintuitive failure mode. I would expect the client would fail and refuse to
> send the request.
>
> TIA!
> Chris
>
> ------------------------------------------------------
>
> http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2790431
>
------------------------------------------------------
http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=2794285
