Re: invoke a script directly by its url

Am 19.03.2008 um 15:30 schrieb Jukka Zitting: You'd break the strict concept of a REST server as you mix resources and representations. If you directly call the representation (the script), you hide the resource inside your script, and the framework (Sling) no longer knows about it. There is

Re: invoke a script directly by its url

Am 19.03.2008 um 15:09 schrieb Edgar Poce: Since you are provinding scripting alternatives to my comment of using wicket I guess usage of strongly typed OO languages such as java to build applications on top of Sling is discouraged, large scale applications are supposed to be written only in scr

Re: invoke a script directly by its url

Hi, Edgar Poce wrote: Hi Alexander, thank you very much for you explanations, I've got on more question. Since you are provinding scripting alternatives to my comment of using wicket I guess usage of strongly typed OO languages such as java to build applications on top of Sling is discouraged,

Re: invoke a script directly by its url

Hi, On Wed, Mar 19, 2008 at 3:51 PM, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > Am 19.03.2008 um 14:28 schrieb Edgar Poce: > > I'm surely missing something, I don't see why running a script > > directly would break REST principles. The script itself is the > > resource and if the user i

Re: invoke a script directly by its url

Sorry to jump in so late, but this conversation is one that I had struggled with as well. After spending a little time speaking with Tobias I finally got it straight. Alexander is right, this does take a bit of a mental switch. For example, in lets look at a blog index page: /blog/january.html

Re: invoke a script directly by its url

Hi Alexander, thank you very much for you explanations, I've got on more question. Since you are provinding scripting alternatives to my comment of using wicket I guess usage of strongly typed OO languages such as java to build applications on top of Sling is discouraged, large scale applications

Re: invoke a script directly by its url

Am 19.03.2008 um 14:28 schrieb Edgar Poce: I'm surely missing something, I don't see why running a script directly would break REST principles. The script itself is the resource and if the user invokes it with a custom selector the representation would be the result of the execution of the given

Re: invoke a script directly by its url

On Wed, Mar 19, 2008 at 9:39 AM, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > Hi Edgar! > > Am 19.03.2008 um 12:34 schrieb Edgar Poce: > > > > IMHO the indirections needed to use scripts as templates are needed > > but only for more advanced use cases. It would be cool if Sling in 15 > >

Re: invoke a script directly by its url

Hi Edgar! Am 19.03.2008 um 12:34 schrieb Edgar Poce: IMHO the indirections needed to use scripts as templates are needed but only for more advanced use cases. It would be cool if Sling in 15 minutes were the second hop, the first hop would be preparing an script with notepad and copying it to s

Re: invoke a script directly by its url

Hi, On Tue, Mar 18, 2008 at 6:29 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > > is there any way to achieve this with sling?, if not what would be the > > recommended practice to create simple crud pages? > > What you could of course do as a workaround is to set the > sling:resourceType

Re: invoke a script directly by its url

Hi Edgar, Pleased to see you here in Sling ;-) Am Dienstag, den 18.03.2008, 13:49 -0300 schrieb Edgar Poce: > Hi, > > I was wondering if there's any way to invoke scripts directly by a > url, a script which is not used as a template for another content. > A simple use case that comes to my min

invoke a script directly by its url

Hi, I was wondering if there's any way to invoke scripts directly by a url, a script which is not used as a template for another content. A simple use case that comes to my mind is a simple CRUD page to administer users. I'd like to invoke the script directly because it won't be reused, it would