Carsten Ziegeler wrote > Justin Edelson wrote > >> So are you suggesting that the resource resolver resolve [workspace]:[path] >> and that Resource.getPath() return this form for non-default workspaces? > Yes, I'm still not sure what the best way is, but I think it's either > the above or it's mounting workspaces under specific paths in the > resource tree. I know that this might create some problems here or > there, but overall it seems to better fit to the resource tree abstraction. > I think Sling is more following the Highlander principle: there can only > be one resource tree. So we have a single (potentially large) resource > tree. We have users and access rights and can control the visibility > etc. through these. > Therefore I'm more in favour of the above solutions. > There might be one problem with having a path like "workspace:path" - converting this into a url: usually without any mapping the resource is directly accessible by its resource path, so can use the resource path to create links without any additional handling. With a colon in the path this wouldn't work anymore - however, the correct way to create link is to use the map() method of the resource resolver. And the resolver could handle this somehow.
Carsten -- Carsten Ziegeler [email protected]
