Hi Oliver,
Oliver Lietz schrieb:
Am Donnerstag, 17. April 2008 schrieb Felix Meschberger:
Hi Oliver,
Hello Felix,
thanks for your detailed explanation and sorry for my late reply. I had to
move development from a dying Mac OS X 10.4 (ppc/32bit) system to a new 10.5
(intel/64bit) system and cannot reproduce the problem anymore. The CND files
(with namespace included) I used for my development are from a working
Magnolia-based project. It works fine now, though I have some more
questions...
Ok. Glad to hear, it works ...
Nevertheless, if you encounter issues, you are very welcome to raise a
JIRA so that we can fix this.
[...]
The ContentLoader from o.a.s.jcr.contentloader doesn't support same name
siblings which is a requirement. It's easy to extend the loader but I'm
unsure about the impact on the rest of Sling. Looks like most parts of Sling
have to be touched to support SNS. Is it worth the effort? Should I stick to
Sling or start a new project?
Well, first of all I don't like SNS as it complicates matters more than
it helps them. See also Rule #4 in David's Model [1] for more info on
this topic.
And yes, you are right. Sling is built around the idea of _not_ having
SNS in that we just ignored the existence of SNS. This does AFAICT not
mean, the Sling won't work with SNS. I can assume that Sling would be
perfectly able to resolve an URL of the form
http://host/content/sns[3]/page.html.
Of course I would be happy, if you would stick with Sling and therefore
am certainly ready to look into any issues you encounter using SNS.
As a first step, providing a patch for the content loader to support SNS
content is certainly a good thing.
Regards
Felix
[1]
http://wiki.apache.org/jackrabbit/DavidsModel#head-1df0224190c265f5156f037eb3f20e314fa6c4a7
