Looks like Wicket Viewer is fetching all objects. How can I know which URL to make a call to to fetch all objects in this context?
Bhargav Golla Developer. Freelancer. B.E (Hons.) Computer Science BITS-Pilani Github <http://www.github.com/bhargavgolla> | LinkedIN<http://www.linkedin.com/in/bhargavgolla> | Website <http://www.bhargavgolla.com/> On Sat, Sep 7, 2013 at 11:30 PM, Bhargav Golla <[email protected]>wrote: > Hi Dan > > Reopening this for more clarification. > > On Mon, Sep 2, 2013 at 11:59 PM, Dan Haywood <[email protected] > > wrote: > >> >> On 1 September 2013 17:54, Bhargav Golla <[email protected]> wrote: >> >>> Hello >>> >>> >> Sorry for the delay in replying, Bhargav... was on vacation. >> >> >> >>> I am trying to add a dependency to a TODO. It's arguments are supposed >>> to by like this {"toDoItem":{"value":"XXXX"}} where XXXX should be some >>> value. >>> >> >> That's the case for scalar values, but it isn't the case for references >> to other objects. >> >> >> >>> Could I know what should be placed in XXXX place to add a ToDo item as a >>> dependency? I tried ID of a ToDo item, but it is giving me this response. >>> { >>> "toDoItem": { >>> "value": "http://localhost:8080/restful/objects/TODO/L_18";, >>> "invalidReason": "Expected a link (because this object's type >>> is not a value) but found no 'href'" >>> }, >>> "x-ro-invalidReason": "Mandatory" >>> } >>> >>> >> So, you almost got it right. As per sec 2.9.2.1 of the RO spec, the >> value must be a json-node with a "href", ie: >> >> { "toDoItem": >> {"value": >> { "href": "http://localhost:8080/restful/objects/TODO/L_18"; } >> } >> } >> >> >> ~~~ >> Your next question, I suspect, will be: "how do I know which hrefs to >> provide?" In the Wicket viewer, we have support for the autoComplete >> facet, and so render a drop-down. In the RO spec v1.0, there is no support >> currently for autoComplete, so there is no easy way to support it. >> >> I am working on v1.1. of the spec that defines this capability. A couple >> of ideas for you in the meantime: >> - extend the dom application to support choices (this is defined in the >> RO spec), and render a drop-down of these >> > Could you explain this idea about extending DOM application more? > >> - cache objects identifiers as they are visited and make them available >> in a drop-down (as "recently viewed") >> - provide some sort of ability to pin or bookmark objects (eg onto a >> "shelf" area) so that they can then be dragged down into the slot >> afterwards. >> >> Dan >> >> >> >> >>> Regards >>> >>> Bhargav Golla >>> Developer. Freelancer. >>> B.E (Hons.) Computer Science >>> BITS-Pilani >>> Github <http://www.github.com/bhargavgolla> | >>> LinkedIN<http://www.linkedin.com/in/bhargavgolla> >>> | Website <http://www.bhargavgolla.com/> >>> >> >> >
