Op 31-8-2012 19:50, Dan Haywood schreef:
> On 31 August 2012 12:32, Minto van der sluis <[email protected]> wrote:
>
>> Hi folks,
>>
>> I wonder what is the best way to interact with the rest interface for my
>> ISIS application.
>
>
> Quick correction on the subject: the json viewer is now called the
> restfulobjects viewer.
>
>
I guess this is the case for the comming release. Since the current docs
on http://incubator.apache.org/isis/documentation.html still mention
json viewer
This also makes me wonder if I should stick with the current release
0.2.0 or move ahead. How stable is the current trunk version?
>
>
>> Most information I could find mention interaction from
>> display technology like javascipt. In my case I need to interact server
>> side.
>>
>
> The intention is that the org.apache.isis.viewer : restfulobjects-applib
> ("RO Applib") will provide this capability.
>
> In fact, a large part of it is there and implemented; the main issue with
> the RO viewer and its applib is just that it is lagging behind the spec,
> and so only implementing v0.52 (or so), rather than the published v1.0.0
>
>
I will have a closer look at the latest/trunk ro-applib. I guess
RestfulRestfulClient is entry point to start from. But to be able to use
it I probably have to switch to using the trunk version.
Can I use the trunk ro-applib for the client and have my Isis
application still use the latest release version?
>>
>> Ofcourse there are numerous client side REST libraries to choose from.
>> However I am probably not the first one trying to do this for an ISIS
>> project. So I wondered how others are doing this and what's the best way
>> to move forward.
>>
>
> As Jeroen notes in his mail, it isn't necessary to use the RO applib.
> However, it is designed to be extensible in a number of ways. For
> example, the JsonRepresentation has "type-safe" subtypes for each of the
> specific representations, eg DomainObjectRepresentation. Or, it can just
> be used as a "bag" of nodes, and access those nodes using an Xpath-like
> notation. Since the applib (and viewer) is based on RestEasy, there's also
> support for templated URLs if you prefer to work in an RPC rather than
> HATEOAS style.
My case is similar to what Jeroen described. We also have an existing
application for which we intend to replace the backend as a proof of
concept.
>
> Speaking slightly selfishly, I'd love you to have a go with using the RO
> applib; it'll help us determine where the gaps and annoyances are for
> "real-life" use.
I could give it a try If I knew were to start. Is the 0.2.0 json viewer
documentation still a good starting point? Since I am lazy ;-) I wonder
if their exists some sample application already. This could give me a
headstart.
>
> Thx
> Dan
>
>
>
>>
>> Regards,
>>
>> Minto van der Sluis
>>
>>
>
--
ir. ing. Minto van der Sluis
Software innovator / renovator
Xup BV
Mobiel: +31 (0) 626 014541
