I do not think this is an errata, though feel free to report it on
OSGi Bugzilla as such. This will make it go through the process.
I think the permission is quite different from the autoimport in R3
because
this is related to security.
If you have permission to export than you could potentially attack the
system
with bad contents. So you seem to be trusted with this package. It
seems therefore
to be strange to not be able to import this package, which is more or
less a random
decision from the bundle's point of view.
I really can't think of a use case where you need EXPORT package
permission
but can not have IMPORT package permission?
Kind regards,
Peter Kriens
On 3 jun 2008, at 13:39, Ikuo Yamasaki 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
