To: dev@sling.apache.org
Subject: Re: Resource Access Tags
On 04.03.2013, at 16:26, Justin Edelson jus...@justinedelson.com wrote:
The new tags are around accessing resources - hence not really
directly related to request processing logic.
But including and forwarding *resources* and *scripts
,
Dan
-Original Message-
From: Felix Meschberger [mailto:fmesc...@adobe.com]
Sent: Tuesday, February 26, 2013 5:19 AM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi,
Am 26.02.2013 um 05:04 schrieb Dan Klco:
Felix,
I like the idea of creating a separate
On Mon, Mar 4, 2013 at 4:30 AM, Felix Meschberger fmesc...@adobe.com wrote:
... sr sounds not too bad. I would have chose resource out of my belly. I
agree sling-resource is probably too long
Maybe res ?
I don't do much JSP so I don't know if it's already used though.
-Bertrand
Hi,
I might be missing something obvious, but what is the driver to put these in a
separate bundle?
Thanks,
Justin
On Feb 25, 2013, at 12:02 PM, Felix Meschberger fmesc...@adobe.com wrote:
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Hi,
Am 04.03.2013 um 15:10 schrieb Justin Edelson:
Hi,
I might be missing something obvious, but what is the driver to put these in
a separate bundle?
Separation of concern ? The current tag lib is about include/forward mostly -
hence request processing logic.
The new tags are around
Hi,
On Mon, Mar 4, 2013 at 10:12 AM, Felix Meschberger fmesc...@adobe.comwrote:
Hi,
Am 04.03.2013 um 15:10 schrieb Justin Edelson:
Hi,
I might be missing something obvious, but what is the driver to put
these in a separate bundle?
Separation of concern ? The current tag lib is about
On Mon, Mar 4, 2013 at 7:26 AM, Justin Edelson jus...@justinedelson.com wrote:
...It doesn't make sense to me to have a
separate taglib than the sling taglib and seems like a
real inconvenience to developers to have to include two different taglib
directives and on deployers to deploy two
: Tuesday, February 26, 2013 5:19 AM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi,
Am 26.02.2013 um 05:04 schrieb Dan Klco:
Felix,
I like the idea of creating a separate Resource API tag library. I think
there's enough functionality there to justify it and it may or may
[mailto:fmesc...@adobe.com]
Sent: Monday, February 25, 2013 12:03 PM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Yet, I wonder whether we should add those tags and EL functions
Hi Dan
Thank you very much. Glancing over it, this looks fine -- a deeper review is
welcome.
Yet, I wonder whether we should add those tags and EL functions to the existing
JSP taglib or whether we should create a Resource API specific tag library ?
WDYT ?
Regards
Felix
Am 22.02.2013 um
namespace for the
Resource API tags? 'sr' or 'resource'?
Thanks,
Dan
-Original Message-
From: Felix Meschberger [mailto:fmesc...@adobe.com]
Sent: Monday, February 25, 2013 12:03 PM
To: dev@sling.apache.org
Subject: Re: Resource Access Tags
Hi Dan
Thank you very much. Glancing over
All,
I've made some additional contributions around the resource access tags, based
on SLING-1500https://issues.apache.org/jira/browse/SLING-1500, which had some
nice features including:
* New FindResources tag, for invoking the
resourceResolver.findResources functionality
*
Hi,
On Wed, Dec 5, 2012 at 9:47 PM, Dan Klco dan.k...@sixdimensions.com wrote:
...
https://issues.apache.org/jira/browse/SLING-2648
I've added my comments there - supplying automated tests will make it
easier for us to integrate your new (and cool!) tags.
-Bertrand
13 matches
Mail list logo
