Hi, >> If you explicitly list the path you see from the source and the bundle contents what exactly you have - without requiring to read the manifest.
Agreed. Although, I´m thinking in a situation that repository were quite deep. I like your propossal: <Sling-Initial-Content>SLING-INF/content;path=/root/location</Sling-Initial-Content> >> Since you are committer, you are cordially invited to create an issue and commit a patch ;-) Thanks, it would be my first Sling issue :-). I´ll do it then. BR, Juanjo. On Tue, May 13, 2008 at 2:08 PM, Felix Meschberger <[EMAIL PROTECTED]> wrote: > Hi, > > Am Montag, den 12.05.2008, 16:18 +0200 schrieb Juan José Vázquez > Delgado: > > >> I agree, but it could be quite annoying have to repeat a few times > the > > base path. > > Agreed. But then, If you explicitly list the path you see from the > source and the bundle contents what exactly you have - without requiring > to read the manifest. On the other hand it may also be confusing... > There are pros and cons and possibly different preferences. > > Therefore: What do you think of something like this: > > (1) put your content into the bundle, e.g. at SLING-INF/content > (2) define the content in the manifest as > > > <Sling-Initial-Content>SLING-INFO/content;path:=/root/location</Sling-Initial-Content> > > This would instruct the content loader to load the content below > SLING-INF/content to the repository below /root/location. > > Since you are committer, you are cordially invited to create an issue > and commit a patch ;-) > > Regards > Felix > > > > > 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 > > > > >
