I believe you can access namespace-prefixed nodes using the
namespace-mangling feature of the resource resolver, try:
/tutorial/_app_content/content/chapter1
You can change the regex used for this mangling in the Felix webconsole
configuration screen for "Apache Sling Resource Resolver"
However, it also sounds like perhaps you don't have an actual "app"
namepace, but rather a node name containing an escaped/transformed
prefix - I'm not familiar enough with Sling to know how this came
about. How did you create this test content tree?
Regards,
Rory
Andreas Hartmann wrote:
Hi Sling devs,
sorry if this basic question has been answered before – I didn't find
anything.
If I want to distinguish JCR item names belonging to my application
from user-generated items, my first idea would be to use a prefix:
/tutorial
/app:content > nt:resource
/content
/chapter1
(How) is this compatible with Sling's URI mapping? I did some tests,
but somehow I couldn't access a prefixed node (like app:content) over
HTTP. Strangely, when I mount the repository via WebDAV, the folder
name is "app/content" (not a hierarchy, but as the name of a single
folder).
Is it discouraged to use node name prefixes in Sling? Should I use a
naming convention instead, e.g. appContent?
TIA!
-- Andreas
