Declarative Services (at least the Felix implementation) seems to look for OSGI-INF under Bundle-ClassPath already.
Yours, Alexey Romanov On Fri, Jun 22, 2012 at 2:43 PM, Balázs Zsoldos <[email protected]> wrote: > Hi, > > the following question came into my mind: > > If we have a WAB where the Bundle-Classpath is WEB-INF/classes shall we load > the OSGI-INF directory from the root of the bundle or from the > WEB-INF/classes directory? > > If we put the OSGI-INF into the root aries-blueprint works. However we > always have to add additional restrictions not to allow the read of this > directory from outside (from the web browser). In this case I think it would > be useful to define the OSGI-INF folder location as the following: It should > be in the bundle classpath not in the root of the bundle. If the bundle > classpath is the root of course it should be at the root of the bundle. > > The same question raises about META-INF/persistence.xml (the default > location). I think it has to be normally at the classpath so at > WEB-INF/classes/META-INF/persistence.xml not in the root of the bundle > otherwise we will face security issues. > > And of course the question is the same for every OSGI based configuration > file like metatype, dynamic services... > > Regards, > Balazs Zsoldos >
