You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Peter Svensson <ps...@gmail.com> on 2008/01/22 17:31:35 UTC
ujax ponderings
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
Re: ujax ponderings
Posted by Peter Svensson <ps...@gmail.com>.
Well, now that I understand what crx is, it feels a bit more OK :) This is
apparently the evolution of the project which Sling forked from to become an
Apache project.
One positive thing is that it has massive documentation, very much geared
towards using Java/JEE as a client to JCR/CRX, but still containing good
info.
I've not been able to install it yet, though. It seems unable to reach its
admin interface.
Cheers,
PS
On Jan 23, 2008 3:24 AM, Torgeir Veimo <to...@pobox.com> wrote:
>
> On 23 Jan 2008, at 02:39, David Nuescheler wrote:
>
> > 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...
>
>
> Note:
>
> "Remote Verification. You acknowledge and agree that the Software may
> contain
> verification and reporting functionality that allows the remote
> reporting of
> your usage of the Software for the purpose of verifying your
> compliance with
> these terms and conditions. "
>
> --
> Torgeir Veimo
> torgeir@pobox.com
>
>
>
>
Re: ujax ponderings
Posted by Torgeir Veimo <to...@pobox.com>.
On 23 Jan 2008, at 02:39, David Nuescheler wrote:
> 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...
Note:
"Remote Verification. You acknowledge and agree that the Software may
contain
verification and reporting functionality that allows the remote
reporting of
your usage of the Software for the purpose of verifying your
compliance with
these terms and conditions. "
--
Torgeir Veimo
torgeir@pobox.com
Re: ujax ponderings
Posted by Alexander Klimetschek <ak...@day.com>.
If you mind using a commercial tool, there is also an open-source
project that offers a web-based JCR explorer/browser like the one in
CRX as well:
http://www.jcr-explorer.org/
Regards,
Alex
Am 22.01.2008 um 18:04 schrieb David Nuescheler:
> hi peter,
>
> On 1/22/08, Peter Svensson <ps...@gmail.com> wrote:
>> Sure, I'm installing it right now. But it feels kind of odd to use a
>> commercial product to be able to understand an Apache project :)
> totally... i think once the packaging and documentation is up
> to par, in my mind there should even be a more efficient way to
> get your hands on ujax directly from apache.
> sorry for the little detour to "day", i am sure in a couple of weeks
> from now this will not be necessary anymore...
>
>> Don't get
>> me wrong, though. I'll use it to try to understand how things work,
>> but am I
>> allowed to use things in ujax and copy them to my Sling
>> installation? How
>> does CRX relate to Sling?
> CRX is our commercial offering around jackrabbit.
> the crx installer that is attached to the blogpost features the
> prerelease of ujax...
> the firststeps.zip should also help to understand things...
>
> you should definitely be able to copy your ujax app to your opensource
> sling install, as a matter of fact even the extracted firststeps.zip
> should
> work in you sling install.
>
> please feel free to contact me directly if you have issue with the
> installer
> and crx, since i am not sure that this is of greater interest for
> this list ;)
>
> sorry again for the detour.
>
> regards,
> david
--
Alexander Klimetschek
alexander.klimetschek@day.com
Re: ujax ponderings
Posted by David Nuescheler <da...@day.com>.
hi peter,
On 1/22/08, Peter Svensson <ps...@gmail.com> wrote:
> Sure, I'm installing it right now. But it feels kind of odd to use a
> commercial product to be able to understand an Apache project :)
totally... i think once the packaging and documentation is up
to par, in my mind there should even be a more efficient way to
get your hands on ujax directly from apache.
sorry for the little detour to "day", i am sure in a couple of weeks
from now this will not be necessary anymore...
> Don't get
> me wrong, though. I'll use it to try to understand how things work, but am I
> allowed to use things in ujax and copy them to my Sling installation? How
> does CRX relate to Sling?
CRX is our commercial offering around jackrabbit.
the crx installer that is attached to the blogpost features the
prerelease of ujax...
the firststeps.zip should also help to understand things...
you should definitely be able to copy your ujax app to your opensource
sling install, as a matter of fact even the extracted firststeps.zip should
work in you sling install.
please feel free to contact me directly if you have issue with the installer
and crx, since i am not sure that this is of greater interest for this list ;)
sorry again for the detour.
regards,
david
Re: ujax ponderings
Posted by Peter Svensson <ps...@gmail.com>.
Sure, I'm installing it right now. But it feels kind of odd to use a
commercial product to be able to understand an Apache project :) Don't get
me wrong, though. I'll use it to try to understand how things work, but am I
allowed to use things in ujax and copy them to my Sling installation? How
does CRX relate to Sling?
Thanks!
Chers,
PS
On Jan 22, 2008 5:39 PM, David Nuescheler <da...@day.com> wrote:
> 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 <ps...@gmail.com> 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
> >
>
Re: ujax ponderings
Posted by David Nuescheler <da...@day.com>.
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 <ps...@gmail.com> 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
>