Hi,
Am Donnerstag, den 20.12.2007, 16:48 +0100 schrieb Michael Marth:
> Sounds great.
>
>
> > This WebDAV module currently supports the Jackrabbit JCR repository,
> > but Sling is meant to run with any JCR repository.
>
>
>
> OK, but can I add: switching the repository to another JCR reposito
Sounds great.
> This WebDAV module currently supports the Jackrabbit JCR repository,
> but Sling is meant to run with any JCR repository.
OK, but can I add: switching the repository to another JCR repository is
comparatively easy (i.e. does not require a recompile)
(I like CRX's Repository Ex
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.
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
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 µsl
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
> target/org.apach
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 high-level goals and requirements
for µsling 2.0.
µsling 2.0 is a preconfigured instance of Sling,
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 :-)
On Dec 18, 2007 2:32 AM, <[EMAIL PROTECTED]> wrote:
> I guess I was thinking that microsling could be viewed as a simplified sling
> programming environment. ...
I agree with that, or maybe more precisely: microsling (once merged)
exposes the parts of Sling that are easiest to use and understand
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 remai
-
From: Felix Meschberger <[EMAIL PROTECTED]>
Date: Tue, 18 Dec 2007 00:24:46
To:sling-dev@incubator.apache.org
Subject: Re: [RT] Shall we merge microsling into Sling?
Probably not quite. If we intend microsling to be an entry level Sling,
we have to make sure, that every script and c
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
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
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
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 thi
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 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
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
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
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
22 matches
Mail list logo
