Initial Bundle installation
---
Key: SLING-138
URL: https://issues.apache.org/jira/browse/SLING-138
Project: Sling
Issue Type: Improvement
Components: Launcher
Reporter: Felix Meschberger
[
https://issues.apache.org/jira/browse/SLING-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-138.
---
Resolution: Fixed
Implemented bootstrap bundle installation in Rev. 605168
Initial Bundle
[
https://issues.apache.org/jira/browse/SLING-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-137.
---
Resolution: Fixed
ScriptResolver is now a separate project scripting/resolver
Break out
[
https://issues.apache.org/jira/browse/SLING-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-110.
---
Resolution: Fixed
After having gotten microsling running with Java Scripting API and
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-134:
---
Assignee: Felix Meschberger
Decoupling resource resolver and resource manager
On Dec 17, 2007 10:01 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I finally managed to make microsling run again and have all integration
tests run successfully in both JDK 5 and JDK6
Thanks for this, confirmed with java 1.5 on macosx.
-Bertrand
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552709
]
Felix Meschberger commented on SLING-134:
-
Modified Sling API in Rev. 605185:
* Removed ResourceManager
At least with µjax we have more control over the client than with
standard web forms, and even then, a concatenation of two
ServletFilters* and a hidden field could make a POST request into a
PUT request. So the server-side development can clearly separate the
concepts.
* ServletFilters:
Sounds good to me, but I would make 500.js and Throwable.js (as the
catch-all-solution) interchangeable, because having GET.js PUT.js
DELETE.js POST.js 404.js 401.js and Throwable.js looks like breaking a
pattern if you just need unspecific, but user-friendly error handling.
regards,
Lars
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552715
]
Felix Meschberger commented on SLING-134:
-
Modified jcr/resource project to reflect the API changes in Rev.
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552717
]
Felix Meschberger commented on SLING-134:
-
Adapted sling/core project in Rev. 605192.
Decoupling resource
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552719
]
Felix Meschberger commented on SLING-134:
-
Adapted scripting/jsp and scripting/jsp-taglib projects in Rev.
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552720
]
Felix Meschberger commented on SLING-134:
-
Adapted sling/sample project in Rev. 605198
Decoupling resource
[
https://issues.apache.org/jira/browse/SLING-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger closed SLING-134.
---
Resolution: Fixed
Sling successfully builds, so I close this issue.
Decoupling resource
Hi,
Am Dienstag, den 18.12.2007, 12:47 +0100 schrieb Lars Trieloff:
Sounds good to me, but I would make 500.js and Throwable.js (as the
catch-all-solution) interchangeable, because having GET.js PUT.js
DELETE.js POST.js 404.js 401.js and Throwable.js looks like breaking a
pattern if you
On Dec 17, 2007 11:00 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz:
people can always add an extra selector to the
Property URL to use a different script.
Yes, or the resource type could be the resource type of the
My idea is:
So, the resolution process would be :
(1) for status codes:
Servlet s = resolveScriptOrServlet(code);
if (s == null) {
s = resolveScriptOrServlet(500);
}
if (s == null) {
s = defaultErrorHandlerServlet;
}
(2) Likewise for Throwables it would be:
I would prefer simple names over FQ names, but perhaps checking the FQ
name first and then the SimpleName would allow us to eliminate all
ambiguity.
regards,
Lars
On 18.12.2007, at 13:28, Bertrand Delacretaz wrote:
Hi,
On Dec 18, 2007 1:16 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
On Dec 18, 2007 12:24 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I rather see microsling as a
pre-canned (stripped-down) Sling...
I agree with microsling being Sling in a smaller box, but I don't
think it is stripped down: if we merge microsling into Sling, all
Sling features remain
Hi all,
As my initial request for discussion of our Community Roles and
Processes definition [1] did not launch a big discussion (apart from
some improvements by Bertrand), I would now like to start the vote on
this document.
The major points of interest in the definition are:
* Every
Hi all,
Am Dienstag, den 18.12.2007, 14:04 +0100 schrieb Bertrand Delacretaz:
I agree that it's not a problem, provided we deliver an easy to start
single jar (or single zip file to expand before running) for
microsling.
Good news is, that this has been possible in Sling for a long time :-)
Am Dienstag, den 18.12.2007, 14:12 +0100 schrieb Tobias Bocanegra:
i don't think that other than a 500.js is needed. or do you have a
valid use case?
Not a use case really, but staying in the line: using 500 for a
Throwable is bridging from an exception over to a status code.
Therefore, I would
[
https://issues.apache.org/jira/browse/SLING-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552748
]
Lars Trieloff commented on SLING-53:
Mindquarry could donate the implementation of this particular filter, if
[
https://issues.apache.org/jira/browse/SLING-53?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552757
]
Bertrand Delacretaz commented on SLING-53:
--
With ujax: I meant only the type of pattern for special
Without going into the details, this means that usling is a
pre-configured distribution of Sling. I'm wondering if we should stick
with the name in this case?
Carsten
Bertrand Delacretaz wrote:
Hi
Wow, V2.0 already :-)
We seem to agree on the need to merge µsling back into Sling, so I
On Dec 18, 2007 2:19 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Just build the launcher/app project with the full profile. You get a
huge (currently 10MB) executable jar file enclosing all bundles to
launche Sling:
$ mvn -P full package
$ java -jar
Replace current errorhandler mechanism by a more flexible one
-
Key: SLING-140
URL: https://issues.apache.org/jira/browse/SLING-140
Project: Sling
Issue Type: Improvement
On Dec 18, 2007 2:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...Without going into the details, this means that usling is a
pre-configured distribution of Sling. I'm wondering if we should stick
with the name in this case?...
Well, we could also try the webapp formerly known as µsling
Bertrand Delacretaz wrote:
On Dec 18, 2007 2:55 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...Without going into the details, this means that usling is a
pre-configured distribution of Sling. I'm wondering if we should stick
with the name in this case?...
Well, we could also try the
Hi,
Am Dienstag, den 18.12.2007, 15:19 +0100 schrieb Carsten Ziegeler:
So I'd keep the name even if it's just the module name of that default
configuration.
Hmm, okay - perhaps over time we come up with different distributions
with different names (and the time for 'catapult' will come, I'm
sounds great.
regards,
david
On 12/18/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
Hi
Wow, V2.0 already :-)
We seem to agree on the need to merge µsling back into Sling, so I
think it' be good to agree on the goals first - feel free to comment
and expand on the following list of
that why i wouldn't check for a exception script at all. since any
exception would result in a 500 that is where the script is then used.
or what other internal errors do you except ?
regards, toby
On 12/18/07, Lars Trieloff [EMAIL PROTECTED] wrote:
I agree. It is also easier to explain that we
On Dec 18, 2007 3:42 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Dienstag, den 18.12.2007, 15:29 +0100 schrieb Tobias Bocanegra:
that why i wouldn't check for a exception script at all. since any
exception would result in a 500 that is where the script is then used.
or what other
Am Dienstag, den 18.12.2007, 15:45 +0100 schrieb Bertrand Delacretaz:
On Dec 18, 2007 3:42 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Dienstag, den 18.12.2007, 15:29 +0100 schrieb Tobias Bocanegra:
that why i wouldn't check for a exception script at all. since any
exception would
+1
Regards
Felix
Am Dienstag, den 18.12.2007, 14:09 +0100 schrieb Felix Meschberger:
Hi all,
As my initial request for discussion of our Community Roles and
Processes definition [1] did not launch a big discussion (apart from
some improvements by Bertrand), I would now like to start the
On Dec 18, 2007 4:37 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...we could make it even simpler: we just
look for an error script or servlet, like this:
Servlet s = resolveScriptOrServlet(error);
if (s == null) {
s = defaultErrorHandlerServlet;
}...
And let the
Am Dienstag, den 18.12.2007, 17:19 +0100 schrieb Bertrand Delacretaz:
On Dec 18, 2007 4:37 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...we could make it even simpler: we just
look for an error script or servlet, like this:
Servlet s = resolveScriptOrServlet(error);
if (s
Hi,
I can only support these ideas because they bring an entry-level Sling
using a subset of the same components as are used in Sling.
Am Dienstag, den 18.12.2007, 14:44 +0100 schrieb Bertrand Delacretaz:
Wow, V2.0 already :-)
Makes sense, as the initial Apache Sling release will also be 2.0.
38 matches
Mail list logo
