Hi all,
I would like to propose to create a ResourceWrapper class in the Sling
API, which is just a simple wrapper around a delegatee resource
analogous to what we have for servlet requests and responses. This
simplifies the creation of pseudo-resources, for example to create
resource based on ano
> I would like to propose to create a ResourceWrapper class in the Sling
> API, which is just a simple wrapper around a delegatee resource
> analogous to what we have for servlet requests and responses. This
> simplifies the creation of pseudo-resources, for example to create
> resource based on an
On Feb 6, 2008 9:26 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...I would like to propose to create a ResourceWrapper class in the Sling
> API, which is just a simple wrapper around a delegatee resource
> analogous to what we have for servlet requests and responses
+1
> Second, I pro
Am Mittwoch, den 06.02.2008, 09:54 +0100 schrieb Tobias Bocanegra:
> > I would like to propose to create a ResourceWrapper class in the Sling
> > API, which is just a simple wrapper around a delegatee resource
> > analogous to what we have for servlet requests and responses. This
> > simplifies the
> > > I would like to propose to create a ResourceWrapper class in the Sling
> > > API, which is just a simple wrapper around a delegatee resource
> > > analogous to what we have for servlet requests and responses. This
> > > simplifies the creation of pseudo-resources, for example to create
> > >
On Feb 6, 2008, at 12:26 AM, Felix Meschberger wrote:
Hi all,
I would like to propose to create a ResourceWrapper class in the Sling
API, which is just a simple wrapper around a delegatee resource
analogous to what we have for servlet requests and responses. This
simplifies the creation of pse
