Hi Slingers,
The Component name, used by Sling to designate objects that render
parts of content, is a bit confusing, especially w.r.t. OSGi
Components which are software modules.
We talked about this at work with Felix, Carsten and others, and we
agree that a more specific name would help in
On 9/19/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...it might
probably better to use http://sling.apache.org/sling/1.0; instead...
I'm for that one as well.
-Bertrand
On 9/26/07, Christophe Lombart [EMAIL PROTECTED] wrote:
... Is it not too early to take a decision ? Why not to experiment
both solution
for a couple of time ?..
Makes sense, totally agreed.
...Bertrand, what do you mean by creating utilities to generate the jcr name ?
Can you give us a
On 10/8/07, Felix Meschberger [EMAIL PROTECTED] wrote:
... The ResourceResolver filter selects the Resource that the current
request applies to.
This is currently called the ContentResolver and a Resource is currently
called Content manifested by an implementation of the Content interface,
Hi Sling team,
(hmmm...long read ahead, sorry about that but I tried to keep it pragmatic ;-)
When talking about Sling to people who don't know it, a reaction that
comes up very often is this stuff looks cool, but I cannot really
figure out what it does.
Looking at the list of bundles [1], I
On 10/9/07, David Nuescheler [EMAIL PROTECTED] wrote:
...Of course I would personally but sling-jcr into sling-core
but i think that's to be expected, considering my
point of view ;)...
By sling-jcr I meant the boring stuff, wrappers and the like, which
would only clutter the core, as the aim
On 10/12/07, Ross Gardler [EMAIL PROTECTED] wrote:
...Can someone tell me (point me at docs) that will enable me to:
- add a source file to the repo
- render that in my browser...
I don't want to distract your from the real thing, but your might want
to have a look at microsling, which
(note also that I'm writing microsling with a small m now - it looks
s bad with a capital M, reminds me of an ugly monster ;-)
-Bertrand
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
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.
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
Hi Roy,
Thanks for the clarification and links - comments inline.
On 10/15/07, Roy T. Fielding [EMAIL PROTECTED] wrote:
...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 tricked into
On 10/15/07, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...We could for example define that adding a slingMethod=PUT parameter
to the request causes SlingServlet.doPut to be called instead of
doPost
To clarify, note that I meant this for the POST method only, this
should *not* be done
On 10/16/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...What is your opinion on this: A separate SlingServlet interface/class
hieararchy or going along the lines of the HttpServlet (yet doing it
better with respect to non-core HTTP methods) ?...
I tend to agree with you guys about using
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
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
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
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
On 10/18/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
..Sorry for trying hard to be a pita :) but again, can we please let all
these discussions take place in the mailing list?...
You're right, sorry about that. We should discuss things here, and
move to Jira once we reach consensus.
On 10/18/07, Tobias Bocanegra [EMAIL PROTECTED] wrote:
The resolver would set the Resource and SlingRequestPathInfo on the
context immediately. ...
...this limits the 'resource resolution' to only work with a sling
request context
I agree with Toby, and also the
void
On 10/18/07, Felix Meschberger (JIRA) [EMAIL PROTECTED] wrote:
...Attachment: SLING-67.patch
Proposed SlingGetServlet and GenericSlingServlet...
I like the idea, and the patch looks good to me, with a few
(hmmm...say some ;-) suggestions:
1) I think we should rename the etc package to helpers
On 10/18/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...// return the main content of the current request
Content getContent();
// return a content address by path
Content getContent(String path) throws SlingException;
// list the children of the
On 10/18/07, Tobias Bocanegra [EMAIL PROTECTED] wrote:
...what about a:
interface ResolvedResource extends Resource {
public String getResolutionPath();
}
Even simpler, we weren't really using Resource.getURI until now, so I
simply changed its comment, and will use it instead:
/**
On 10/19/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...Many methods in microsling are defined to throw Exception
That's me ;-)
I know many people find this wrong (do you have more info/references
on why?) but I like to do that in widely-used interfaces, as it allows
the implementation
On 10/19/07, David Nuescheler [EMAIL PROTECTED] wrote:
...Would an initial content loader mechanism be useful?...
Shouldn't you be able to to just put any static file into the repository via
webdav, and then just use the webdav url to retrieve it again?..
You're right, so the actual problem
On 10/18/07, Tobias Bocanegra [EMAIL PROTECTED] wrote:
...you would add a 'selector' for different views of the same content.
eg:
/content/blog/entry1.html for view and
/content/glob/entry1.edit.html for editing...
That's correct, see ScriptFilenameBuilderTest for examples of how this
On 10/18/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...Bertrand Delacretaz:
2) For names I'd prefer SlingGetServlet (or maybe
SlingReadonlyServlet?) and SlingFullServlet, to better express the
relationship between them.
Or SlingReadWriteServlet :-) ?
As you note, that sounds a bit
On 10/19/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...We have the Servlet Request Dispatcher, which IMHO should be used in
microsling (using as much of existing/known API as possible)...
Sure, that was the plan.
...Thus a
script may easily do
Hi,
Thanks Felix for the API changes - the packages structure looks very
understandable to me now, I think that's a great step in making Sling
easy to understand.
On 10/27/07, Felix Meschberger [EMAIL PROTECTED] wrote:
Bertrand:
...7) SlingScriptEngine
Should we have two eval() methods?
Hi,
Looking at the current sling-api:
public SlingHttpServletRequestWrapper(SlingHttpServletRequest delegatee)
I would have expected
public SlingHttpServletRequestWrapper(ServletRequest delegatee)
And then the constructor can complain if the delegatee (why not call
that simply wrappedRequest
Hi Torgeir,
On 10/29/07, Torgeir Veimo [EMAIL PROTECTED] wrote:
...2. Generalise the Servlet into a sort of View component. The best
analogy is probably Struts' ActionForward class
...My main concern is that I'm interested in seeing model resolution and
view resolution separated. I
I have added a RequestDispatcherOptions class (really just a Map, with
some constants for well-known options names) to these methods:
1) in SlingHttpServletRequest:
RequestDispatcher getRequestDispatcher(Resource resource,
RequestDispatcherOptions options)
2) in SlingScriptHelper
void
On 10/30/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...If I read and understand everything
correctly, freemarker is made available under a BSD license [1], which
is assumed to be a class A third party license by Apache [2]
That's also my understanding.
...We would just have to add
Hi,
With the sling-api discussions coming to a close (AFAIU), we'll be
able to port microsling to the new sling-api soon.
Here's my suggestion for the Maven modules to use for that:
microsling (main microsling module)
- microsling-core (depends on sling-api)
- microsling-commons
On 10/30/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...I would place this not in the trunk directly but in the project using
the respective library. Just like for example I have done in the
content-jcr project
You're right - I suggest leaving that NOTICE file where it is now, so
as
On 10/30/07, Lars Trieloff [EMAIL PROTECTED] wrote:
...I still think having a
level of inheriance and aspect-orientation in rendering is something
we want, because it eases the development process
I agree that this might be useful in some cases - but do you think we
can achieve this
On 10/31/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...One simple solution would
be to have all script engines in microsling but make them optional
...The detection if the required stuff is available in the classpath could
be done by just trying to instantiate the engine always. If
On 10/31/07, David Nuescheler [EMAIL PROTECTED] wrote:
(3) how about using the workspace itself as an extension mechanism...
something like:
/.microsling/script-engines/esp
/.microsling/script-engines/fm
/.microsling/script-engines/rb
... which would host all the mapping information
On 10/31/07, Marcel Reutegger [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
1) Our own simple jar service provider mechanism
microsling looks for jar files providing a file like [1] , using our
own simple ServiceLoader class (like Felix suggests, that's about 10
lines of code
On 10/31/07, Padraic Hannon [EMAIL PROTECTED] wrote:
...I thought David's suggestion seemed spot on. Let's use JCR to register
script types, this way the project becomes extremely simple, ...
...If people agree I can have
something a patch put together as an example?..
Why not...my concern
On 11/1/07, Michael Marth [EMAIL PROTECTED] wrote:
One comment: if we package microsling Ajax client (can we find another
name, please?) ...
no, no, not names again...arrg..please... ;-)
We could use microjax as a nickname maybe.
...with microsling it makes even more
On 11/1/07, Lars Trieloff [EMAIL PROTECTED] wrote:
...I know how much we all value these discussions, but as RJAX is taken
and a really bad acronym and microajax is already taken by another
framework, what about using
AJACs - Asynchronous Javascript and Content
don't like that, the
On 11/1/07, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...in order to avoid all those private copies of the json.org classes in
various modules (and own projects), I moved the json classes to an own
bundles which is now referenced from the others
Great - I'll need that Real Soon Now for
On 11/2/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...While thinking about the scripting in the real Sling yesterday I
thought, that we should not only support scripts in the repository but
also in the OSGi bundles
Sounds good.
...So Carsten and me came to the conclusion to take up
Hi Felix,
On 11/2/07, Felix Meschberger [EMAIL PROTECTED] wrote:
... think if the resource type is
set to a certain value, it is not appropriate for the ResourceResolver
to modify this value
Agreed, and also about using the nodetype as is if no slingResourceType is set.
I've just made
On 11/5/07, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Freitag, den 02.11.2007, 09:49 +0100 schrieb Bertrand Delacretaz:
On 11/2/07, Felix Meschberger [EMAIL PROTECTED] wrote:
...One simple (stupid ?) solution would be to add a getInputStream()
method
to the resource...
Could
On Nov 20, 2007 11:17 AM, David Nuescheler [EMAIL PROTECTED] wrote:
...public interface JcrResource extends Resource {...
can we make it NodeResource ?
Good idea, as it points to a Node, not a JCR ;-)
-Bertrand
On Nov 20, 2007 3:37 AM, Jukka Zitting [EMAIL PROTECTED] wrote:
...+1 I would even go as far as questioning the need for the Resource
interface in the first place; why not use Node instead?...
Having a Resource helps people think in REST terms, so I like that
even though the API could be a bit
On Nov 20, 2007 10:58 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Let us keep the Resource completely abstract...
I like that.
...public interface JcrResource extends Resource {
Node getNode();
}..
Ok
... public interface MappedResource extends
On Nov 20, 2007 11:54 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Why not replace the SlingScript interface providing
a Resource by a ScriptResource interfaces:
...The question of course is: Is a Script a Resource ??...
Not always IMHO, we might have (mini-)scripts which come from
On Nov 20, 2007 11:58 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...OcmMappedResource as in
Object-Content-Mapping-Mapped-Resource sounds a bit weird. ...
...I agree that MappedResource sounds kind of generic. After all, it is an
interface and should be somewhat generic, right ?...
On Nov 19, 2007 8:57 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
On Nov 18, 2007 5:01 PM, David Nuescheler [EMAIL PROTECTED] wrote:
...Personally, I would rather just go for a straight, more direct
extension-based
resolution than engaging in the whole mimetype business
+1
Agreed,
On Nov 16, 2007 9:29 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Freitag, den 16.11.2007, 11:22 -0500 schrieb Bertrand Delacretaz:
...Maybe make the
default servlet available in the SlingRequest, or some of its methods
to help with that
I would not do that, this would violate
On Nov 21, 2007 12:48 PM, Jukka Zitting [EMAIL PROTECTED] wrote:
...I would only split the URI (path) to two parts, the resource path and
anything that comes after that. Basically, the resolver would start
with a context node and a URI path (without any leading parts like the
webapp or
On Nov 20, 2007 11:38 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I suggest we drop the ScriptEngine interface in favore of using Java
Scripting
I'm +1 on that, assuming that runs on JDK 1.5 (which IIUC would be ok
with BSF 3, as you mentioned).
-Bertrand
On Nov 23, 2007 12:40 AM, Alexandru Popescu ☀
[EMAIL PROTECTED] wrote:
...I am pretty sure that the JDK
is/will be more stable than BSF
The problem is that java script is only available in JDK 1.6, whereas
(IIUC) BSF provides support in JDK 1.5, which is our current JDK
target.
-Bertrand
Hi,
I'll very probably have an opportunity to coach some young trainees
that want to find out how open source works, in the next few weeks.
The idea is to have these people (ages 15-18 I guess, so not much
prior technical knowledge) help us by working on relatively simple and
well-defined tasks
Hi,
Just noticed that mvn integration-test fails in microsling-core, for
some reason the web container is not started.
All tests pass using mvn jetty:run and mvn -o
-PnullMicroslingProfile test, so it's really only the
cargo-maven2-plugin that does not work.
I'll have a look tomorrow, in the
On Nov 26, 2007 6:38 PM, Bertrand Delacretaz [EMAIL PROTECTED] wrote:
...Just noticed that mvn integration-test fails in microsling-core...
Fixed in revision 598583 - that was simply the tests include/exclude
paths that were wrong, adding a new package yesterday under
integration made
On Nov 27, 2007 12:18 PM, Tobias Bocanegra [EMAIL PROTECTED] wrote:
...i'm strongly against removing the class files from the repository.
from my experience it is very valuable if you can remove the classes
remotely
Do you need to be able to remove individual class files from the
On Nov 29, 2007 3:10 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...While it is probably useful in certain situations to have the session
available, I am not so sure, whether this should be documented and
become part of the API or whether we should just have it. ...
For microsling the JCR
On Nov 29, 2007 5:32 PM, Michael Marth [EMAIL PROTECTED] wrote:
I meant to covert just the stuff within the %% brackets into
document.write() and leave the rest untouched. So, your example would
produce sthg like:
p class=scriptdocument.write(item.color)/script...
Which is not valid
On Nov 29, 2007 8:31 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...we could either add a
getJcrSession() method to SlingHttpServletRequest, or at least make
the attribute name a constant to expose its use
...would define a attribute name as a constant in Sling and microsling and
Hi Ricky,
...Hello. I signed up on google code to make logos for Sling and
microsling
Welcome! For those of us who are not following GHOP, see
http://code.google.com/p/google-highly-open-participation-asf/issues/detail?id=2
(and people, note that additional tasks can be suggested at
On Nov 30, 2007 8:15 AM, Tobias Bocanegra [EMAIL PROTECTED] wrote:
...examples apache project logos/sites i like:...
Note that for most of these, if you squint and look at them with eyes
barely open, you still recognize the logo. I think that's an important
factor in logo design.
-Bertrand
Hi Carsten,
(sorry about replying so late, the thread was sitting in my must act
on this folder for too long ;-)
On Nov 25, 2007 12:58 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...currently the API
does not have any other reference to JCR! So, introducing this one
single dependency does
On Nov 30, 2007 12:54 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...I'm a little bit unhappy that noone responded to my response in this
thread and now the code is already changed
Sorry about that - I have replied in the API thread, let's make sure
we agree (although I think we shouldn't
Hi,
I think recursively going up the path in the
MicroslingResourceResolver can lead to confusion and redundant GET
URLs.
Do we really need suffixes? I'm still a bit confused about their goals
for GET requests.
Maybe we could simplify the Resource resolution, here's a suggested
example where
On Nov 30, 2007 8:22 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...An extended more flexible solution would be something like this:
public interface Resource {
// get this resource as an object of the type or null if not
possible
T T adaptTo(ClassT
On Dec 1, 2007 12:16 AM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Felix Meschberger wrote:
... T T adaptTo(ClassT type);...
...Yepp, that looks very good to me, +1...
Yee-haaw! We have closure I guess ;-)
-Bertrand
Hi Ricky,
On Dec 1, 2007 12:08 AM, Ricky E. [EMAIL PROTECTED] wrote:
http://www.kb3llm.org/apachelogo/pro3.jpg
...does it look better than the first two?
Yes, I like it much better! Maybe you could move the feather up a bit
, so that it collides more with the word Sling. And maybe
softening
Hi Felix,
On Dec 4, 2007 8:34 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Here's a proposal for a different way of resolving scripts, with three
possible cases:
a) Node has a valid sling:resourceType property
The resource type is the value of this property, which, to be valid,
On Nov 30, 2007 6:49 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
...So for an existing /content/foo node:
/content/foo - HTTP status code 200
/content/foo.html - 200, extension=html
/content/foo.print.a4.html - 200, extension=html, selectors=print.a4
ok with all of these
Hi,
I was looking for a way to allow people to play with microsling, that
requires only a JVM, and created a setup based on Jetty's start.jar
utility (lifted^H^H^H^H inspired from what Solr does [1]).
To build and test this example config, see
On Dec 5, 2007 1:30 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
...I was a little bit unclear :) I think we should use
the 2.4 version in most of our poms, so we can assure that only 2.4 api
is used. However if we implement servlet api somewhere, this module
should use the 2.5 version (if I
to gray levels, it would
be good to improve this.
-Bertrand
again the link: http://www.kb3llm.org/apachelogo/pro3d.jpg
and micro:
http://www.kb3llm.org/apachelogo/pro3dm.jpg
Let me know so we can finish this case on GHOP.
Thanks.
--
Bertrand Delacretaz
http://www.codeconsult.ch
Hi,
On Dec 6, 2007 9:50 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...Rather I suggest, we define an extensible input validation system,
which is used mainly by the microjax handling but may also be used other
consumers of client supplied input data
Agreed
...I have been looking at
Hi,
I'm not sure how logging is configured for microsling, when running
mvn test or mvn integration-test.
The logs are way too verbose now, I'd like to have minimal output when
tests pass, and lots of debugging stuff in a log file to analyze when
tests fail.
I could find out, but if someone
On Dec 10, 2007 10:49 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
Am Montag, den 10.12.2007, 09:36 + schrieb [EMAIL PROTECTED]:
...SLING-114 - output an newline after each out.write(...); to make it
easier to post-process generated javascript code
While it definitely makes the
Hi,
Having access to ServletContext in scripts would be useful to allow
scripts to access java objects initialized by other servlets.
If we agree, I'll add a suitable constant to SlingScriptEngine, and
change ScriptHelper and MicroslingScriptResolver accordingly.
-Bertrand
On Dec 12, 2007 2:24 PM, Philipp Koch [EMAIL PROTECTED] wrote:
request.getServiceLocator().getService(ServletContext.class);
and what about microsling?
Coming up, see https://issues.apache.org/jira/browse/SLING-136
-Bertrand
On Dec 10, 2007 10:23 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
Hi,
Am Freitag, den 07.12.2007, 05:02 -0800 schrieb Bertrand Delacretaz
One interesting feature would to use an additional search path that depends
on the beginning of the resource path, for example for a resource found
On Dec 10, 2007 12:25 PM, Juan José Vázquez Delgado
[EMAIL PROTECTED] wrote:
(1) encode the requested version as part of the URL, such as
/content/some/resource.html;v=1.0 (for the resolve(request) method)...
...IMHO, there are some situations which we can need to retrieve the same
On Dec 11, 2007 6:50 PM, Felix Meschberger [EMAIL PROTECTED] wrote:
Hi,
Am Dienstag, den 11.12.2007, 17:03 + schrieb [EMAIL PROTECTED]:
+
+// SLING-133: do not resolve scripts for Properties, we want to
use our default
+// renderers for them (TODO: having that test
On Dec 13, 2007 9:24 AM, Felix Meschberger [EMAIL PROTECTED] wrote:
...I posted a proposal for a definition of our Community Roles and
Processes in our Wiki [1]. The central points of this document are the
following:...
Thanks - I added some clarifications in there, and reworked some parts
On Dec 12, 2007 5:52 PM, Michael Marth [EMAIL PROTECTED] wrote:
Re issue 1):
we could have a 404 handler script that kicks in when a non-existing
resource is requested
Good idea. Do you have a suggestion about how to select which 404 script to use?
Assume I have dropped some scripts
On Dec 13, 2007 3:13 AM, Roy T. Fielding [EMAIL PROTECTED] wrote:
On Dec 12, 2007, at 1:10 PM, Bertrand Delacretaz wrote:
How about
/content/some/resource.html/s:version:1.4/s:lang:fr/somefile.pdf
where suffixes starting with s: are reserved for Sling usage?
yuck. A general
On Dec 12, 2007 10:52 PM, Carsten Ziegeler [EMAIL PROTECTED] wrote:
Bertrand Delacretaz wrote:
...That's why MicrojaxPostServlet uses a POST to /foo/* to mean create
new child node under /foo, and POST to /foo to mean update /foo.
Using PUT instead would be cleaner of course, but browsers
http://www.slingcommunity.com/
But we're the only Apache Sling, no worries ;-)
-Bertrand
in a 404 the system would look in
/a/b/c
/a/b
/a
/error
For 404.esp
WDYT?
Paddy
Sent via BlackBerry from T-Mobile
-Original Message-
From: Bertrand Delacretaz [EMAIL PROTECTED]
Date: Thu, 13 Dec 2007 13:58:40
To:sling-dev@incubator.apache.org
Subject
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
content
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 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 small,
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
automatically
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
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.bsf
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 right
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
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
1 - 100 of 1339 matches
Mail list logo
