BJ, Mirko, and Peter Thank you for your comments.
On Wed, 4 Jun 2008 07:59:08 +0200 Peter Kriens <[EMAIL PROTECTED]> wrote: Peter> I do not think this is an errata, though feel free to report it on Peter> OSGi Bugzilla as such. This will make it go through the process. Peter> Peter> I think the permission is quite different from the autoimport in R3 Peter> because Peter> this is related to security. Peter> Peter> If you have permission to export than you could potentially attack the Peter> system Peter> with bad contents. So you seem to be trusted with this package. It Peter> seems therefore Peter> to be strange to not be able to import this package, which is more or Peter> less a random Peter> decision from the bundle's point of view. Peter> Peter> I really can't think of a use case where you need EXPORT package Peter> permission Peter> but can not have IMPORT package permission? I understand what Peter and BJ mean and I agree in the point that no use case where you need EXPORT but not IMPORT package permission. On that basis, in my opinion, changing the description of section 3.5.4 as follows would be less inconsistent: [R4.1] > "In order to be allowed to import a package (except for packages > starting with java.), a bundle must have PackagePermission[<package-name>, > IMPORT]." [new] (as in R3) > In order to be allowed to import a package (except for packages > starting with java.), a bundle must have PackagePermission[<package-name>, > EXPORT| IMPORT]. Best regards, ======= Ikuo YAMASAKI _______________________________________________ OSGi Developer Mail List osgi-dev@mail.osgi.org https://mail.osgi.org/mailman/listinfo/osgi-dev
