[
https://issues.apache.org/jira/browse/SLING-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lars Trieloff updated SLING-68:
---
Attachment: sling-sample-logging-dependency.patch
This patch adds the sling-log bundle as a compile tim
Compile fails for sling-sample due to missing dependencies
--
Key: SLING-68
URL: https://issues.apache.org/jira/browse/SLING-68
Project: Sling
Issue Type: Bug
Environment: Mac
> conceptual stuff:
>
> - I was wondering how I can have several templates for one content type. I
> could work around this issue in my very simple case, but how can I have e.g.
> an edit template and a view template for a blog entry (depending on some
> request parameter or so)?
you would add a '
[
https://issues.apache.org/jira/browse/SLING-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-55.
--
Resolution: Fixed
Fixed in revisions 586028 and 586029, the ServiceLocator is currently u
Hi,
Bertrand has asked me to give some user feedback on microsling on this list.
I have been playing with microsling for just one day now and did not have a
look at (full) sling, yet, but from my very limited understanding so far the
issues I found should apply to sling as well.
First of all, I v
On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Well, thinking along these lines: Why do we need a Resource and
> ResourceResolver in the first place then ? ...
Technically, as we're limiting ourselves to JCR content, we don't
really need a Resource, you're right.
But currentl
On 10/18/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> ...what about a:
>
> interface ResolvedResource extends Resource {
>public String getResolutionPath();
> }
Even simpler, we weren't really using Resource.getURI until now, so I
simply changed its comment, and will use it instead:
Am Donnerstag, den 18.10.2007, 16:26 +0200 schrieb Bertrand Delacretaz:
> On 10/18/07, Felix Meschberger (JIRA) <[EMAIL PROTECTED]> wrote:
>
> > ...Attachment: SLING-67.patch
> > Proposed SlingGetServlet and GenericSlingServlet...
>
> I like the idea, and the patch looks good to me, with a few
>
[
https://issues.apache.org/jira/browse/SLING-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-60:
-
Summary: SlingRequestPathInfo values must depend on path used by
ResourceResolver (was: UR
Am Donnerstag, den 18.10.2007, 16:36 +0200 schrieb Bertrand Delacretaz:
> On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ...// return the main content of the current request
> > Content getContent();
> > // return a content address by path
> > Conte
On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...// return the main content of the current request
> Content getContent();
> // return a content address by path
> Content getContent(String path) throws SlingException;
> // list the children of
On 10/18/07, Felix Meschberger (JIRA) <[EMAIL PROTECTED]> wrote:
> ...Attachment: SLING-67.patch
> Proposed SlingGetServlet and GenericSlingServlet...
I like the idea, and the patch looks good to me, with a few
(hmmm...say "some" ;-) suggestions:
1) I think we should rename the "etc" package to
Felix Meschberger schrieb:
> Hi all,
>
> The current Component API contains the following methods in the
> SlingRequest interface:
>
> // return the main content of the current request
> Content getContent();
> // return a content address by path
> Content getConte
Hi all,
The current Component API contains the following methods in the
SlingRequest interface:
// return the main content of the current request
Content getContent();
// return a content address by path
Content getContent(String path) throws SlingException;
On 10/18/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...we could also drop the SlingRequestPathInfoParser as the (default)
> ResourceResolver would by backtracking the path be able to keep track of
> the path parts and create a SlingRequestPathInfo object as a byproduct
I don't like th
On 10/18/07, Tobias Bocanegra <[EMAIL PROTECTED]> wrote:
> > The resolver would set the Resource and SlingRequestPathInfo on the
> > context immediately. ...
> ...this limits the 'resource resolution' to only work with a sling
> request context
I agree with Toby, and also the
void reso
Tobias Bocanegra wrote:
>
> hi, once again this is display logic. the 'main' component script
> knows that it needs to display
> a header and a footer, so basically you do a:
>
>
>
> then the footer component will check if it actually has content, and
> if not, it fetches it from the parent pag
Am Donnerstag, den 18.10.2007, 14:39 +0200 schrieb Tobias Bocanegra:
> > > this limits the 'resource resolution' to only work with a sling
> > > request context. what if i want to resolve a resourse without context
> > > ? e.g. when i want to check if a respective resource exists?
> > > i would hav
> > this limits the 'resource resolution' to only work with a sling
> > request context. what if i want to resolve a resourse without context
> > ? e.g. when i want to check if a respective resource exists?
> > i would have to create a fake request context ?
>
> Well, you always have the SlingReque
Am Donnerstag, den 18.10.2007, 13:56 +0200 schrieb Tobias Bocanegra:
> > public interface ResourceResolver {
> > void resolveResource(SlingRequestContext context) throws
> > SlingException;
> > }
> >
> > The resolver would set the Resource and SlingRequestPathInfo on the
> > context immediately.
> public interface ResourceResolver {
> void resolveResource(SlingRequestContext context) throws
> SlingException;
> }
>
> The resolver would set the Resource and SlingRequestPathInfo on the
> context immediately. And I think, the SlingRequestContext probably needs
> a "backlink" to the request i
How about this:
public interface ResourceResolver {
void resolveResource(SlingRequestContext context) throws
SlingException;
}
The resolver would set the Resource and SlingRequestPathInfo on the
context immediately. And I think, the SlingRequestContext probably needs
a "backlink" to the request
[
https://issues.apache.org/jira/browse/SLING-67?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-67:
---
Attachment: SLING-67.patch
Proposed SlingGetServlet and GenericSlingServlet
> Provide extensib
On 10/18/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi, I have thought a little bit more about template handling and I came
> to the conclusion that we could add support for it to the heart of
> Sling. (For now, I'm refering to the "old" sling - current trunk, we can
> adapt this to the new
Provide extensible default Servlets
---
Key: SLING-67
URL: https://issues.apache.org/jira/browse/SLING-67
Project: Sling
Issue Type: New Feature
Components: microsling
Reporter: Felix Mes
Hi,
I'm starting work on SLING-60, and I think I'll add this new interface
to the microsling.api package:
public interface ResourceResolver {
Result resolveResource(HttpServletRequest req) throws Exception;
public static class Result {
...
public Resource getResource();
// Indi
[
https://issues.apache.org/jira/browse/SLING-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz reassigned SLING-60:
Assignee: Bertrand Delacretaz
> URI path split is content dependent
> ---
[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-61.
-
Resolution: Fixed
Ok, after some better use cases discussions (see sling dev list), we are all
hap
Tobias Bocanegra wrote:
>>> ...So, you have a node storing all documents as sub nodes. Now, you want to
>>> make a view on these documents containing just a bunch of them. With the
>>> references, you create a "view node" containing several reference nodes
>>> and are done
>> The header/footer
Hi, I have thought a little bit more about template handling and I came
to the conclusion that we could add support for it to the heart of
Sling. (For now, I'm refering to the "old" sling - current trunk, we can
adapt this to the new stuff later on).
Ok, let's start with an example. Assume you hav
> > ...So, you have a node storing all documents as sub nodes. Now, you want to
> > make a view on these documents containing just a bunch of them. With the
> > references, you create a "view node" containing several reference nodes
> > and are done
> The header/footer example was a bit scary t
ok. thanks for the clarification.
in this case, i would avoid the auth filter as well.
regards, toby
On 10/17/07, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Mittwoch, den 17.10.2007, 16:49 +0200 schrieb Tobias Bocanegra:
> > i disagree...eg. when running in a appserver that does authenticat
On 18 Oct 2007, at 07:59, Carsten Ziegeler wrote:
Sorry for trying hard to be a pita :) but again, can we please let all
these discussions take place in the mailing list?
I think it's easy to first discuss a topic in the mailing list and
then
create a jira which either sums up the discussion
On 10/18/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> ..Sorry for trying hard to be a pita :) but again, can we please let all
> these discussions take place in the mailing list?...
You're right, sorry about that. We should discuss things here, and
move to Jira once we reach consensus.
-Bert
Sorry for trying hard to be a pita :) but again, can we please let all
these discussions take place in the mailing list?
I think it's easy to first discuss a topic in the mailing list and then
create a jira which either sums up the discussion or references the
mailing list archives.
Carsten
Felix
35 matches
Mail list logo
