Hi all,
Prompted by a proposal in the Chickens, eggs and stars thread [1], I
propose a revised error handling concept for Sling. First, though, I
present the current implementation.
Current implementation
--
Currently Sling (the core project) defines a ErrorHandlerServlet. T
I guess I was thinking that microsling could be viewed as a simplified sling
programming environment. If so it could be viewed as just a sling bundle which
provides script and other services to get people up and running quickly.
Paddy
Sent via BlackBerry from T-Mobile
-Original Message
Probably not quite. If we intend microsling to be an entry level Sling,
we have to make sure, that every script and content used in microsling
may still be used in Sling. Therefore, I rather see microsling as a
pre-canned (stripped-down) Sling.
For example: Sling has a Configuration Admin Service
Am Montag, den 17.12.2007, 15:06 -0800 schrieb Padraic Hannon:
> I can see the distinction between application and resource type
> specific handling, however, given that multiple apps may handle the
> same resource types differently and thus have different exception
> handling needs how do yo
So for a microsling application project one would just use a different
configuration for the DefaultServlet? Could this be handled via
resource types? Using something like a microsling base node type for
application resources (this just popped into my head and could be
silly)? Integrating W
I can see the distinction between application and resource type
specific handling, however, given that multiple apps may handle the
same resource types differently and thus have different exception
handling needs how do you see this working? How do you feel about
using the script path (whic
Hi,
Agreed. About the only two differences I actually see between Sling and
microsling are:
* Full-Blown and powerfull DefaultServlet (ujax amongst other things)
* very simple setup/startup
The first issue may probably easily be "ported" to Sling in a separate
DefaultServelt project. The b
Hi,
Am Montag, den 17.12.2007, 11:15 +0100 schrieb Bertrand Delacretaz:
> The overall goall is to allow users, without using any tools other
> than a set of application files, a WebDAV client and a web browser, to
> copy and start a microsling application, here's the scenario:
>
> 1. User starts
Am Mittwoch, den 12.12.2007, 17:52 +0100 schrieb Michael Marth:
> Re issue 1):
>
> we could have a 404 handler script that kicks in when a non-existing
> resource is requested. This script could decide what to do (because the
> desired behaviour is app specific). For your blog example of for a wik
Am Freitag, den 14.12.2007, 19:59 +0100 schrieb Tobias Bocanegra:
> > Why not use something like custom headers like X-HTTP-Method and a
> > servlet filter to wrap PUTs in POSTs?
> >
> > As we control the client API, this is a cleaner way to do this IMHO.
>
> but we do not control the client. the
Hi,
Am Donnerstag, den 13.12.2007, 14:14 +0100 schrieb Carsten Ziegeler:
> >
> > 1) MicrojaxPostServlet uses /foo/* with the POST method, where * means
> > "create a child node with a generated name under /foo".
> >
> > I think we agree that this is ok.
> >
> Thanks for the explanation - this a
Hi all,
I finally managed to make microsling run again and have all integration
tests run successfully in both JDK 5 and JDK6.
Will fix JSP support tomorrow.
Regards
Felix
Am Montag, den 17.12.2007, 17:46 +0100 schrieb Felix Meschberger:
> Hi all,
>
> After my update to the Java Scripting API
On Dec 17, 2007 5:39 PM, <[EMAIL PROTECTED]> wrote:
> ...That is what I was thinking as well. I'll make a JIRA ticket?..
Sure, feel free to do that!
-Bertrand
> -Original Message-
> From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
>
> Date: Mon, 17 Dec 2007 16:14:48
> To:sling-dev@incuba
Anthing I can do to help?
Paddy
Sent via BlackBerry from T-Mobile
-Original Message-
From: Felix Meschberger <[EMAIL PROTECTED]>
Date: Mon, 17 Dec 2007 17:46:12
To:Sling Developers
Subject: microsling broken
Hi all,
After my update to the Java Scripting API of today, microsling is
b
That is what I was thinking as well. I'll make a JIRA ticket?
Paddy
Sent via BlackBerry from T-Mobile
-Original Message-
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
Date: Mon, 17 Dec 2007 16:14:48
To:sling-dev@incubator.apache.org
Subject: Re: scriptable error handling (was: Chicken
One could walk the resource type tree as well this would keep the content and
scripts in different trees.
Paddy
Sent via BlackBerry from T-Mobile
-Original Message-
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
Date: Mon, 17 Dec 2007 09:52:22
To:sling-dev@incubator.apache.org
Subject
I think this is a great idea!
Paddy
Sent via BlackBerry from T-Mobile
-Original Message-
From: "Bertrand Delacretaz" <[EMAIL PROTECTED]>
Date: Mon, 17 Dec 2007 10:33:56
To:sling-dev@incubator.apache.org
Subject: [RT] Shall we merge microsling into Sling?
Hi,
I think microsling is no
Hi all,
After my update to the Java Scripting API of today, microsling is
broken. I am currently working on getting it up and running again
Sorry for any inconvenience.
Regards
Felix
On Dec 17, 2007 3:35 PM, Lars Trieloff <[EMAIL PROTECTED]> wrote:
> ...Sorry no, by content tree I meant the part of the repository that is
> used to store scripts, not the actual content. It can be confusing
> when everything is content
Ok, agree then!
> ...So the idea is to put the 404.js r
Sorry no, by content tree I meant the part of the repository that is
used to store scripts, not the actual content. It can be confusing
when everything is content.
So the idea is to put the 404.js right next to the html.js. If I
request something.xhtml, 404.js will be excecuted. Similarily
Hi,
Oops. True, I stumbled upon this issue myself. I fixed it by just
deploying the respective parent project to my local repository. I also
wrote to the BSF-dev list about this.
It would probably be a good idea to go to bsf snapshot until the parent
project is in the maven repos. Will do that ri
On Dec 17, 2007 1:22 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...I just migrated microsling (was easy, actually) but did not run the
> integration tests yet
Thanks - I tried to build the whole thing but sling/scripting/api fails:
Failed to resolve artifact.
GroupId: org.apache.bs
Hi Betrand,
I just migrated microsling (was easy, actually) but did not run the
integration tests yet.
Regards
Felix
Am Montag, den 17.12.2007, 12:50 +0100 schrieb Bertrand Delacretaz:
> Hi Felix,
>
> On Dec 17, 2007 12:46 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> > I started committin
Hi Felix,
On Dec 17, 2007 12:46 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> I started committing the changes to implement SLING-110...
>- microsling : Not migrated yet...
Are the other modules ready to allow microsling to be migrated?
If so I can do that this afternoon.
-Bertrand
Hi all,
I started committing the changes to implement SLING-110 [1] (convert to
Java Scripting API). This causes the current build to fail in the
following parts:
- scripting/jsp : Not migrated yet
- microsling : Not migrated yet
The rest should still build.
Regards
Felix
[1] https://iss
Break out ScriptResolver implementation into separate project
-
Key: SLING-137
URL: https://issues.apache.org/jira/browse/SLING-137
Project: Sling
Issue Type: Improvement
[
https://issues.apache.org/jira/browse/SLING-137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned SLING-137:
---
Assignee: Felix Meschberger
> Break out ScriptResolver implementation into separate pr
[
https://issues.apache.org/jira/browse/SLING-110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-110:
Component/s: API
This issue also has an influence on the Sling API
> Update Script System t
Torgeir Veimo wrote:
>
> On 17 Dec 2007, at 20:03, Bertrand Delacretaz wrote:
>
>>> ...Would this enable microsling to run without any OSGi framework at
>>> all?...
>>
>> No, but as Carsten says in his "synchronicity" email (we didn't talk
>> about that off-list before, honest ;-), the Apache Fel
On 12/17/07, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
>
> On 17 Dec 2007, at 20:03, Bertrand Delacretaz wrote:
>
> >> ...Would this enable microsling to run without any OSGi framework
> >> at all?...
> >
> > No, but as Carsten says in his "synchronicity" email (we didn't talk
> > about that off-lis
On Dec 17, 2007 11:05 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz:
> > ...A simple mechanism might be to detect (with JCR observation) when
> > *.sysview.xml files are loaded into the repository, and import them
> > automat
On 17 Dec 2007, at 20:03, Bertrand Delacretaz wrote:
...Would this enable microsling to run without any OSGi framework
at all?...
No, but as Carsten says in his "synchronicity" email (we didn't talk
about that off-list before, honest ;-), the Apache Felix OSGi runtime
is quite small, and sta
Hi Betrand,
Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz:
> On Dec 15, 2007 10:19 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
>
> > ...Am Mittwoch, den 12.12.2007, 17:00 +0100 schrieb Bertrand Delacretaz:
> > > One important goal is being able to drop a microsling appli
On Dec 17, 2007 10:55 AM, Torgeir Veimo <[EMAIL PROTECTED]> wrote:
> ...Would this enable microsling to run without any OSGi framework at all?...
No, but as Carsten says in his "synchronicity" email (we didn't talk
about that off-list before, honest ;-), the Apache Felix OSGi runtime
is quite sma
Hi Bertrand,
Am Montag, den 17.12.2007, 10:04 +0100 schrieb Bertrand Delacretaz:
> I like the idea, though if we want this in microsling we'll need some
> configuration mechanism (which could be part of the autoexec script
> mentioned above).
Hmm, such configuration would probably be placed in th
On 17 Dec 2007, at 19:33, Bertrand Delacretaz wrote:
I think microsling is now ready to become just a specific
configuration of Sling.
I'm pretty sure we can graft the microsling stuff on Sling as a set of
OSGi bundles, without requiring any OSGi knowledge from beginners, and
keep microsling'
+1 - Funny, I didn't read ths mail before I send mine (I spent the whole
weeking drafting it and now Bertrand beat me by ten minutes...)
Carsten
Bertrand Delacretaz wrote:
> Hi,
>
> I think microsling is now ready to become just a specific
> configuration of Sling.
>
> That would save us the ex
The Apache Sling project basically consists of three parts: the API,
Sling and Microsling. The API defines the general system contracts and
interfaces. Sling and Microsling are two implementations of the API;
Microsling has been introduced initially as an educational tool to show
how Sling works fo
Hi,
I think microsling is now ready to become just a specific
configuration of Sling.
That would save us the extra work (and potential community
fragmentation) (and user indecision) (and fuzzy "marketing" message)
that comes with having two similar-but-still-different codebases.
I'm pretty sure
On Dec 15, 2007 10:19 AM, Felix Meschberger <[EMAIL PROTECTED]> wrote:
> ...Am Mittwoch, den 12.12.2007, 17:00 +0100 schrieb Bertrand Delacretaz:
> > One important goal is being able to drop a microsling application...
>
> The classical bootstrap problem. In Sling we solved this with a initial
> c
On Dec 14, 2007 6:10 PM, Lars Trieloff <[EMAIL PROTECTED]> wrote:
> ...I think this is the best proposal,
>
> put the 404.esp (or 401.esp or 500.esp for this purpose) into the
> content tree, and all matching errors will look for a script ascending
> the content tree. If nothing can be found, the d
41 matches
Mail list logo
