On 10/11/2011 16:51, Johan Andries wrote:
Hi,
it would be cool if the Javascript application I'm working on was able
to support all functionality present in the Claims example before I
put it online. There is one thing left and I think it has to do with
transient objects.
Great to hear you're making such good progress. Definitely looking
forward to seeing what you've come up with.
The newToDo() method on ToDoItemRepositoryDefault does an explicit
persist() on the object representation returned by
newTransientInstance(). The object that is returned by the POST to the
action invoke resource returns a full-fledged object that I can
continue to work with.
The newClaim() method on ClaimRepositoryDefault does not call
persist() on the object returned by newTransientInstance() and that's
probably why the returned object representation is rather anemic.
There's no link of type "self" and the actions on the object do not
point to an action invoke resource to do anything meaningful with it.
(The action newEmployee on EmployeeRepositoryDefault has the same behaviour.)
Am I missing something, or has this not yet been implemented in the JSON viewer?
No, you're not missing anythingI just haven't got around to implementing
it yet. Sounds like I need to put it to the top of the todo pile!
By the way, on Tuesday I'm doing a lightning talk (10 minutes!) on RO in
London. If you thought your viewer was in a fit state to show off, I'd
love to give it an audience?
Cheers
Dan
Kind regards,
Johan.
