Oh boy, this look complex.
The code in RO-tck looks like some sort of meta programming. I am
looking for a piece of code to create a new domain object using
RO-applib. But I have a hard time digesting what's there.
Can someone give me some more hints (hopefully a snippet)
Regards,
Minto
Quoting Dan Haywood <[email protected]>:
On 1 September 2012 10:29, Minto van der sluis <[email protected]> wrote:
Should stick with the current release
0.2.0 or move ahead. How stable is the current trunk version?
It's pretty stable; starting to move towards getting a release out in the
next month or two.
And, what's new in trunk is the JDO object store, which may (perhaps)
replace the SQL objectstore, at least in the short-term.
Also, the v0.2.0 release holds an incomplete cut of the RO viewer (whatever
was implemented back in Feb).
~~~
If you do decide to track trunk, you might find it easiest to fork my
github copy of Isis [1]
I will have a closer look at the latest/trunk ro-applib. I guess
RestfulRestfulClient is entry point to start from.
Yes, org.apache.isis.viewer.restfulobjects.applib.RestfulClient.
This lets you use either a HATEOAS or a templated URL approach.
But to be able to use
it I probably have to switch to using the trunk version.
Not sure; I think you'll find that 0.2.0 does have something. Even so, I
do recommend that you switch to trunk
>
> 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.
The tests aren't a bad place to look; you'll find these in
restfulobjects-tck.
Admittedly, these have been knocked-about a bit and so quite a few are
currently are @Ignore'd. However,
the
org.apache.isis.viewer.restfulobjects.tck.resources.home.HomePageResourceTest_accept
runs and passes. (It also uses the isisWebServerRule which bootstraps the
web.xml within an integration test).
Hope that helps some
Dan
[1] https://github.com/danhaywood/apache-isis
