hi peter, to me this looks like there is no /ujax-test node in your repository. could that be? i am not sure where the ujax-test creates its nodes...
btw. for generic ujax prototyping i usually use these installers here: http://dev.day.com/microsling/content/blogs/main/microjax.html which make things a lot more transparent since there is a jcr explorer that comes with it... anyway, since you want to build top of trunk this might be all that valuable... regards, david On 1/22/08, Peter Svensson <[EMAIL PROTECTED]> wrote: > Hi all, > > I've now managed to compile and install the stand-alone version of > microsling from the repo. Very well polished process. I'm very impressed :) > Now, I'm trying out some moves with the ujax.js library which a friendly > soul has provided, to see if I can grok more what it is doing. > > I've done the following; > > 1) I've run the ujax-test from the Sling start page, which ran OK > 2) I've seen that a new directory under my mountpoint is created, called > ujax-test. > 3) I try to do the following in my html-based client; > > var root = ujax.getContent("/ujax-test"); > console.log("root ujax node is "+root); > console.dir(root); > > And I get an empty object, because; > > 22.01.2008 22:46:56 *INFO * MicroslingResourceResolver: Path '/ujax- > test.json' does not resolve to an Item (MicroslingResourceResolver.java, > line 363) > > > And I wonder what I'm missing. Thankful for help, > > Cheers, > PS >
