I agree. I is kinda weird, I know. I stumbled about that some time ago but didn't paid to much attention, because it didn't impose any security risk, as long as you know about it. However, I also think it would be better to change it in order to fit the rest of the framework behavior. It seems more logical to me.
Cheers, Mirko On Tue, Jun 3, 2008 at 1:39 PM, Ikuo Yamasaki <[EMAIL PROTECTED]> wrote: > Hi OSGi Experts, > > In the spec R4.1, section 3.5.6 says > > "Exporting a package does not imply the import of that same package (in > Release 3, an export did imply an import).". > > In addition, section 3.5.4 says > > "In order to be allowed to import a package (except for packages > starting > with java.), a bundle must have PackagePermission[<package-name>, > IMPORT]." > > Section 6.1.18, however, says > > "PackagePermission has two actions: > EXPORT and IMPORT. The EXPORT action implies the IMPORT action". > > I guess the description of 6.1.18 is a kind of errata. > What do you think of it ? > > --------------------- > NTT Cyber Solutions Laboratories > > Ikuo YAMASAKI > E-mail: [EMAIL PROTECTED] > TEL +81-46-859-8537 FAX +81-46-855-1282 > > > _______________________________________________ > OSGi Developer Mail List > osgi-dev@mail.osgi.org > https://mail.osgi.org/mailman/listinfo/osgi-dev > _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
