In our Resource objects, after processing a PUT, we use the Result's
constructor that takes a status and a representation so that our client can get
the complete representation of the object it just put (in our case getting the
ID value just assigned for newly created objects).  Unfortunately our
representation doesn't make it back to the requesting client.  We've traced
through the code and it seems that in the Handler class, in the handlePut (and
handlePost) the Result's Representation is never used.

  We've been able to fix this for us by copying the code from the Handler class
into our extended handler adding the line:

response.setEntity(result.getEntity());

into the handlePut method that we copied from Handler.

  Is it intentional that the Representation field of the Result should be
ignored?  If so, why?  If not, is this the right way to fix this problem?  Could
it be incorporated into the RC1 release?

  Thanks,

  Randy



Reply via email to