"You can put the path as content structure into your bundle" >> Yes, this had been my first approach.
"It works well if other bundles "create" the same base path as well, eg. /some/generic/path/anotherapp" >> I agree, but it could be quite annoying have to repeat a few times the base path. BR, Juanjo. On Mon, May 12, 2008 at 2:31 PM, Alexander Klimetschek <[EMAIL PROTECTED]> wrote: > You can put the path as content structure into your bundle. For example, > if > you use <Sling-Initial-Content>SLING-INF/content</Sling-Initial-Content>, > and you want something under /some/generic/path/myapp, you create > src/main/resources/SLING-INF/content/some/generic/path (typically as > nt:folder) and put your myapp stuff below that. It works well if other > bundles "create" the same base path as well, eg. > /some/generic/path/anotherapp. > > IMHO all paths in the JCR should follow a clear convention and not rely on > other bundles or whatever. > > Regards, > Alex >
