[
https://issues.apache.org/jira/browse/SLING-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-58.
--
Resolution: Fixed
Support has been added and this can now be closed.
Add support for templated
URI path split is content dependent
---
Key: SLING-60
URL: https://issues.apache.org/jira/browse/SLING-60
Project: Sling
Issue Type: Improvement
Components: microsling
Reporter: Felix
I agree, that we might want to wait for a real-life request.
On the other hand it is not only the end-users fault if not the correct
methods could be used, though browsers are probably the major number of
culprits. Many times it is just a question of firewall limitation which
can by no means be
[
https://issues.apache.org/jira/browse/SLING-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535432
]
Bertrand Delacretaz commented on SLING-60:
--
Ok, I see your point...I started looking at the Sling code before
[
https://issues.apache.org/jira/browse/SLING-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535433
]
Bertrand Delacretaz commented on SLING-60:
--
(moving the discussion to the dev list)
URI path split is
On 10/17/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Could we please discuss things in the mailing list and not in Jira...
Sure, let me restate what I said in JIRA-60 here:
I agree with what Felix says in JIRA-60, about the RequestPathInfo
(selectors, extension, suffix, etc) being dependent
Hi guys,
I agree, that we might want to wait for a real-life request.
On the other hand it is not only the end-users fault if not the correct
methods could be used, though browsers are probably the major number of
culprits. Many times it is just a question of firewall limitation which
can by
I completely agree with respect to not using a Filter for
ResourceResolution. Lets make the ResourceResolver a service called by
the SlingRequestContext on demand (btw, the SlingRequestContext must
then probably have a reference to the request, right ?).
Regards
Felix
Am Mittwoch, den
Hi all,
Currently, we love using filtering in both Sling and microsling: Every
part of request processing is implemented using a filter. This was not
always the case: In the days when Sling was still private, there was no
filtering at all.
Probably we must come to a mix of both: There are some
[
https://issues.apache.org/jira/browse/SLING-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-57.
--
Resolution: Fixed
This has been implemented and the issue can be closed.
Resource: retarget
Felix Meschberger wrote:
Hi all,
Currently, we love using filtering in both Sling and microsling: Every
part of request processing is implemented using a filter. This was not
always the case: In the days when Sling was still private, there was no
filtering at all.
Probably we must come
I have the same feeling here. Filter are flexible. Specially for making
processing like authencitation
I would like to say that microsling is very simple to understand as it is. I
like the combinaison of the different serlvets filters. Cool great job.
On 10/17/07, Carsten Ziegeler [EMAIL
On 10/17/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...Lets make the ResourceResolver a service called by
the SlingRequestContext on demand...
cool
...btw, the SlingRequestContext must
then probably have a reference to the request, right ?)
Yes, agreed.
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned SLING-61:
-
Assignee: Carsten Ziegeler
Rendering of references within the repository
Rendering of references within the repository
-
Key: SLING-61
URL: https://issues.apache.org/jira/browse/SLING-61
Project: Sling
Issue Type: New Feature
Components: Core
On 10/17/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...So for now, I personally tend to go with filters except where something
is really required for Sling core to work. There we could use an
explicit service instead
I think that's a very good criteria: if something's always required
[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-61.
-
Resolution: Fixed
Add a new node type and corresponding components/content.
Rendering of
[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12535552
]
Felix Meschberger commented on SLING-61:
suggest to remove this.
-1
Maybe the use case does not convince
[
https://issues.apache.org/jira/browse/SLING-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reopened SLING-61:
Reopen the issue for further consideration.
Carsten, could you please comment ? Thanks.
Am Mittwoch, den 17.10.2007, 09:39 +0200 schrieb Carsten Ziegeler:
I agree for resource and content resolution. But I'm not sure about
authentication. Having a filter which does the authentication is very
transparent. If we are using the servlet filter interface for these
filters, its easy to
JCR Mapping does not handle jcrDefaultValue
---
Key: SLING-63
URL: https://issues.apache.org/jira/browse/SLING-63
Project: Sling
Issue Type: Bug
Reporter: Carsten Ziegeler
The
On 10/17/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...Let's consider an example with a page node which has a header, footer
and content node. Rendering of the page node is always the same (header,
content, footer). Now, with these references it's possible to reference
parts of the page
Felix Meschberger wrote:
Am Mittwoch, den 17.10.2007, 09:39 +0200 schrieb Carsten Ziegeler:
I agree for resource and content resolution. But I'm not sure about
authentication. Having a filter which does the authentication is very
transparent. If we are using the servlet filter interface for
[
https://issues.apache.org/jira/browse/SLING-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler closed SLING-63.
-
Resolution: Fixed
JCR Mapping does not handle jcrDefaultValue
Am Mittwoch, den 17.10.2007, 16:49 +0200 schrieb Tobias Bocanegra:
i disagree...eg. when running in a appserver that does authentication
sling does not need the default http auth filter, but maybe a
jaas-auth filter or sso filter or whatsoever.
bottom line: the authentication mechanism needs
[
https://issues.apache.org/jira/browse/SLING-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-65:
---
Component/s: microsling
Add RequestParameter abstraction
[
https://issues.apache.org/jira/browse/SLING-64?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-64:
---
Attachment: SLING-64.patch
Proposed changes
Refactor Servlets and Script resolution
[
https://issues.apache.org/jira/browse/SLING-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-65.
--
Resolution: Fixed
Added RequestParameter and RequestParameterMap interfaces and getter to
28 matches
Mail list logo