You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Bertrand Delacretaz <bd...@apache.org> on 2007/10/11 18:44:35 UTC
Microsling, first shot, feedback is welcome
Hi Sling community,
I think the current revision of
http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
is worth having a look at if you're interested in the current API /
redesign discussions.
Fifteen minutes should be enough to build it and have a look at how it
works, provided you have a JDK 1.5, Maven 2.0.7 and a WebDAV client
installed. The README.txt explains how to run it.
I have attached the current microsling webapp homepage (which explains
what it is in more detail) to
https://issues.apache.org/jira/browse/SLING-47, just in case.
-Bertrand
Re: Microsling, first shot, feedback is welcome
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/11/07, Christophe Lombart <ch...@gmail.com> wrote:
> ...I will try to be more implied in the couple of days on Sling.
> Maybe a good exercise for myself is to implement the ocm mapping here....
That would be way cool, feel free to hack as much as needed!
-Bertrand
Re: Microsling, first shot, feedback is welcome
Posted by Christophe Lombart <ch...@gmail.com>.
On 10/11/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>
> On 10/11/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>
> > I think the current revision of
> > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
> > is worth having a look...
>
> Forgot to mention that the current version does not use the OCM
> mapping - I'm not too familiar with that and would have needed more
> time to implement it, so for now it's raw JCR.
>
> Using OCM should be easy though, as long as the resource resolver and
> the rendering scripts are consistent with each other. The Resource
> abstraction allows any Object to be selected as the current resource
> to process.
I will try to be more implied in the couple of days on Sling.
Maybe a good exercise for myself is to implement the ocm mapping here.
Patches are welcome, and committers should feel free to commit changes
> directly, of course.
>
> -Bertrand
>
Re: Microsling, first shot, feedback is welcome
Posted by David Nuescheler <da...@day.com>.
wow! congrats....
looks great, and works just fine.
way less than 15 minutes, though... ;)
regards,
david
On 10/11/07, Bertrand Delacretaz <bd...@apache.org> wrote:
> On 10/11/07, Bertrand Delacretaz <bd...@apache.org> wrote:
>
> > I think the current revision of
> > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
> > is worth having a look...
>
> Forgot to mention that the current version does not use the OCM
> mapping - I'm not too familiar with that and would have needed more
> time to implement it, so for now it's raw JCR.
>
> Using OCM should be easy though, as long as the resource resolver and
> the rendering scripts are consistent with each other. The Resource
> abstraction allows any Object to be selected as the current resource
> to process.
>
> Patches are welcome, and committers should feel free to commit changes
> directly, of course.
>
> -Bertrand
>
Re: Microsling, first shot, feedback is welcome
Posted by Bertrand Delacretaz <bd...@apache.org>.
On 10/11/07, Bertrand Delacretaz <bd...@apache.org> wrote:
> I think the current revision of
> http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
> is worth having a look...
Forgot to mention that the current version does not use the OCM
mapping - I'm not too familiar with that and would have needed more
time to implement it, so for now it's raw JCR.
Using OCM should be easy though, as long as the resource resolver and
the rendering scripts are consistent with each other. The Resource
abstraction allows any Object to be selected as the current resource
to process.
Patches are welcome, and committers should feel free to commit changes
directly, of course.
-Bertrand
Re: Microsling, first shot, feedback is welcome
Posted by Tobias Bocanegra <to...@day.com>.
hi,
cool. but i'm missing one level of indirection in the script
resolution filter (as felix already mentioned). i think that this
content-to-script mapping is not enough flexible to handle complex
content structures.
nevertheless, nice work!
regards, toby
On 10/11/07, Felix Meschberger <fm...@gmail.com> wrote:
> Hi Betrand,
>
> Cool !
>
> "ScriptResolution" works somewhat differently as in current Sling, where
> the Component (aka Servlet) is resolved from the Content (aka Resource)
> and either directly implements the actions or selects the concrete
> script for the request from a limited set of scripts (generally one to
> only a very few number). As such the "presentation framework"
> integrations (VelocityTemplatesServlet, RhinoJavascriptServlet) operate
> in the "background" at the service of the Component and its script
> depending on the script selected.
>
> I am also not sure, whether script resolution according to the resource
> path is actually a good idea (of course it serves as a simple
> placeholder for a general principle).
>
> So further discussion should probably concretate on
> Servlet/ScriptResolution, right ?
>
> Or am I missing something ?
>
> Regards
> Felix
>
>
> Am Donnerstag, den 11.10.2007, 18:44 +0200 schrieb Bertrand Delacretaz:
> > Hi Sling community,
> >
> > I think the current revision of
> > http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
> > is worth having a look at if you're interested in the current API /
> > redesign discussions.
> >
> > Fifteen minutes should be enough to build it and have a look at how it
> > works, provided you have a JDK 1.5, Maven 2.0.7 and a WebDAV client
> > installed. The README.txt explains how to run it.
> >
> > I have attached the current microsling webapp homepage (which explains
> > what it is in more detail) to
> > https://issues.apache.org/jira/browse/SLING-47, just in case.
> >
> > -Bertrand
>
>
--
-----------------------------------------< tobias.bocanegra@day.com >---
Tobias Bocanegra, Day Management AG, Barfuesserplatz 6, CH - 4001 Basel
T +41 61 226 98 98, F +41 61 226 98 97
-----------------------------------------------< http://www.day.com >---
Re: Microsling, first shot, feedback is welcome
Posted by Felix Meschberger <fm...@gmail.com>.
Hi Betrand,
Cool !
"ScriptResolution" works somewhat differently as in current Sling, where
the Component (aka Servlet) is resolved from the Content (aka Resource)
and either directly implements the actions or selects the concrete
script for the request from a limited set of scripts (generally one to
only a very few number). As such the "presentation framework"
integrations (VelocityTemplatesServlet, RhinoJavascriptServlet) operate
in the "background" at the service of the Component and its script
depending on the script selected.
I am also not sure, whether script resolution according to the resource
path is actually a good idea (of course it serves as a simple
placeholder for a general principle).
So further discussion should probably concretate on
Servlet/ScriptResolution, right ?
Or am I missing something ?
Regards
Felix
Am Donnerstag, den 11.10.2007, 18:44 +0200 schrieb Bertrand Delacretaz:
> Hi Sling community,
>
> I think the current revision of
> http://svn.apache.org/repos/asf/incubator/sling/whiteboard/microsling
> is worth having a look at if you're interested in the current API /
> redesign discussions.
>
> Fifteen minutes should be enough to build it and have a look at how it
> works, provided you have a JDK 1.5, Maven 2.0.7 and a WebDAV client
> installed. The README.txt explains how to run it.
>
> I have attached the current microsling webapp homepage (which explains
> what it is in more detail) to
> https://issues.apache.org/jira/browse/SLING-47, just in case.
>
> -Bertrand