Felix Meschberger wrote:
Agreed. In fact, bundleresource is probably also an extension...
Maybe :)
We might want to start thinking of required and optional extensions ;-)
Because some extensions are required and used by the launchpad and some
extensions are just there for demo and other purposes...
Yes, I thought of this as well, but couldn't come up with a good
explanation and categories :( If we just have "extensions" this will
grow to a very large number over time. But on the other hand it's just a
directory grouping, so we can change this later on, without any problems.
Hmm... I have my reservations with the name "core-components". First it
is long - and I don't like long names and second: This would give a
groupId of o.a.s.core.components and an bundle symbolic name of
org.apache.sling.core.components.core for the (today's) sling/core
bundle ...
But we could of course rename the sling folder to core and rename the
sling/core module to core/engine - because that module essentially
contains the main request processing machinery.
Might work.
The question still remains: What is really "core" ? The Sling API in
fact would be core, what else ? Maybe we should change completely ? Move
sling/core to a top-level engine bundle (besides api the only toplevel
bundle. And rename the current sling directory to servlets - because it
just contains the servlet resolver as well as the get and post servlets.
:) Yes, I had this idea as well and so far it seems to be the best
option. So, let's move core to top level as "engine", move the
extensions from the current "sling" dir to "extensions" and rename
"sling" to "servlets".
Sounds good to me.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
