proposal on the Jackrabbit Dev List. See the
proposal guide for a description of the expected proposal content.
Abstract
Sling is a framework to develop content centric web applications based
on the idea of modularizing the rendering of HTTP resources.
Proposal
Sling allows easy development of web
Sling to the
> Apache Incubator with a goal of becoming an Apache Jackrabbit
> subproject. Discuss this proposal on the Jackrabbit Dev List. See the
> proposal guide for a description of the expected proposal content.
>
>
> Abstract
> Sling is a framework to develop conten
On 8/8/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Hi Alex,
>
> Am Mittwoch, den 08.08.2007, 17:03 +0300 schrieb Alexandru Popescu ☀:
> > Very interesting initiative Felix! Still, I am wondering why this
> > would not start as a Jackrabbit contrib project, and I don't think I
> > have seen t
Hi Alex,
Am Mittwoch, den 08.08.2007, 17:03 +0300 schrieb Alexandru Popescu ☀:
> Very interesting initiative Felix! Still, I am wondering why this
> would not start as a Jackrabbit contrib project, and I don't think I
> have seen this in the attached proposal.
The reason for not simply adding it
Hi Noel,
Am Mittwoch, den 08.08.2007, 23:12 -0400 schrieb Noel J. Bergman:
> > As such each request URL addresses a Content object which in turn
> > resolves to a Component, which finally is responsible for handling
> > the request and providing a response.
>
> And this differs from a Servlet/Por
Felix Meschberger wrote:
> Noel J. Bergman:
> > > As such each request URL addresses a Content object which in turn
> > > resolves to a Component, which finally is responsible for handling
> > > the request and providing a response.
> > And this differs from a Servlet/Portlet, how?
> With Servlet
On 8/11/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Felix Meschberger wrote:
>
> > Noel J. Bergman:
>
> [... snip ...]
>
>
> Seems to me that you might want to consider a binding for JSR-286 Portlets
> (using the Event mechanism to deliver the content to be rendered), rather
> than create a to
Hi Noel,
> Seems to me that you might want to consider a binding for JSR-286 Portlets
> (using the Event mechanism to deliver the content to be rendered), rather
> than create a totally new UI component framework. I can't see any reason
> why the nested includes would be an issue.
>
> Just a tho
Am Donnerstag, den 09.08.2007, 09:27 -0700 schrieb Eelco Hillenius:
> > I would like to propose a new Apache project named Sling. The proposal
> > text is attached to this message and can also be found at [1].
>
> +1.
Thanks :-)
> It seems to be primarily focussed on content delivery, not so muc
Felix Meschberger wrote:
> As Alex also pointed out, the goal is to have a flexible framework to
> allow for different bindings.
Ah, that was not clear from the proposal. I thought that you were planning
to define your own, new, component model for delivering the content back to
the requestor.
I would just add that JSR-311 might also be an option.
As an aside (and since you folks are on the Expert Group), do we
know if
JAX-RS will be under a suitable specification license, or has Sun
encumbered
it as they have other Sun-led specifications?
We don't know. We won't implement JSR
11 matches
Mail list logo
