Maybe I don't have the right paradigm. Here is what I would expect to
be able to do (with my limited knowledge of sling).
Imagine that I have a resources type 'employee'.
I have understood that with a particular URL, sling will resolve it
and find a particular employee node and will give this node to an ESP,
a JSP or a servlet that will render it.
That's nice if I want to see all the properties of a single employee on my page.
But what If I want to list all employees in a page or as a result of
an AJAX call? Did I have to use the url of the parent node of all the
employee and map that to a rendering script that I have to write ? Is
there any default rendering for list ?
And what if I only want a sublist (as a result of a query for instance) ?
2008/7/19 Bertrand Delacretaz <[EMAIL PROTECTED]>:
> Hi,
>
> On Sat, Jul 19, 2008 at 5:14 PM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
>> ...How can we play with multiple nodes : list of nodes, queries, filters
>> or node coming from 2 completely different path...
>
> Not sure what you mean by that - a Sling script can include the
> rendering of other nodes by using the include function, for example in
> ESP:
>
> sling.include("/content/foo.html")
>
> And that has some options such as forcing a specific resource type,
> for example to render the current node using a different rendering
> script for navigation.
>
> Does that help? If not, please give more details as to what you're
> trying to achieve.
>
> -Bertrand
>
--
Gilles Scokart
