[
https://issues.apache.org/jira/browse/SLING-48?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
christian updated SLING-48:
---
Attachment: sling-core-component-nt.patch
patch containing a suggested fix
wrong content classname in
On 10/14/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...Regarding the resource: I think, we should provide the JCR item to which
the request URL resolved with a proper method, such as Item getItem();
and leave the Object getDate(); method to the object mapping. ..
Fine with me, although
On 10/14/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...As such microsling would have a MicroSlingServlet which has pretty much
everything wired and no OSGi, that is no real lifecycle management and
extensibility...
Just a small thing to add here: microsling is extensible indeed, at
least
Am Montag, den 15.10.2007, 14:00 +0200 schrieb Bertrand Delacretaz:
What I like about the doGet, doPost, doPut, etc.. methods in the
current microsling SlingServlet interface is that they help people
think in terms of HTTP methods.
Sounds reasonable indeed.
We could for example define that
Am Montag, den 15.10.2007, 14:03 +0200 schrieb Bertrand Delacretaz:
On 10/14/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...(2) I am not sure whether resolving the script with the request
extension is useful. Rather I would use the selectors of the request
URL (the dot-separated parts
Am Montag, den 15.10.2007, 14:14 +0200 schrieb Bertrand Delacretaz:
On 10/14/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...Regarding the resource: I think, we should provide the JCR item to which
the request URL resolved with a proper method, such as Item getItem();
and leave the
On 10/15/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...The problem is, that we might want both, the JCR item and the mapped
object. If the getData method would return either of both, how would we
access the other ?...
You're right, we need both getData() and getItem() in the resource.
[
https://issues.apache.org/jira/browse/SLING-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534848
]
Felix Meschberger commented on SLING-48:
Thanks for reporting.
We are currently investigating a major
[
https://issues.apache.org/jira/browse/SLING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-47:
-
Component/s: (was: Core)
microsling
microsling - simple webapp to
microsling: add a RequestFilter that computes the desired Content-Type for the
response
---
Key: SLING-49
URL: https://issues.apache.org/jira/browse/SLING-49
microsling: complete the SlingRequestContext information
Key: SLING-50
URL: https://issues.apache.org/jira/browse/SLING-50
Project: Sling
Issue Type: Improvement
Components:
[
https://issues.apache.org/jira/browse/SLING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-47.
--
Resolution: Fixed
Marking this issue resolved as the basic webapp works - we'll track
Hi Sling team,
As you have probably noticed, I have created a few JIRA issues with
component=microsling [1], to track the ongoing work.
The goal at this point is to make microsling good enough for us to
decide if it can actually be a standalone module *and* the basis for
the Sling OSGi request
[
https://issues.apache.org/jira/browse/SLING-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-49:
-
Component/s: microsling
microsling: add a RequestFilter that computes the desired
[
https://issues.apache.org/jira/browse/SLING-47?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz updated SLING-47:
-
Summary: microsling - simple webapp to demonstrate the core principles of
Sling (was:
[
https://issues.apache.org/jira/browse/SLING-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bertrand Delacretaz resolved SLING-49.
--
Resolution: Fixed
Implemented in revision 584800
microsling: add a RequestFilter that
microsling: SlingScriptResolver should use more user-friendly script names
--
Key: SLING-52
URL: https://issues.apache.org/jira/browse/SLING-52
Project: Sling
Issue
I seem to have failed to get my point across when I last visited
Basel and we talked about what can and cannot be done in a selector.
The original Web design notes forbid the use of GET for any action
that is considered to have side-effects, because such an
implementation allows users to be
thanks for this clarification.
but how i see the current design of (micro)sling - there is not any
intention of 'storing' actions in the uri. of course a user can still
code some 'actions' in his script - but this would not be the fault of
sling. the 'selectors' are primarily used to resolve to a
19 matches
Mail list logo
