Hi Richard,
Richard S.Hall wrote:
I don't think I fully understand your concerns around exporting an
entire package. As you mentioned, what's get exported in 277 module is
in terms of classes and the information is in the module metadata, and
I
think we can probably determine the packages associated with these
exported classes and treat these packages as "exported packages" from
the OSGi perspective. There is no split package allowed in 277 module,
so I think each of these exported packages would be an entire package.
The point is that an OSGi exported package FOO specifically means that
all public classes in the FOO package are accessible to importers. Such
an export is not the same as a 277 module that just happens to export a
class in its export signature from the FOO package. Without cracking
open the module, there is no way to tell if its export signature
contains all public classes from the FOO package (i.e., the entire
package).
-> richard
I think there is a misunderstanding here. Both JSR 277 and OSGi export
all "accessible" classes in a package. JSR 294 changes what accessible
means from "public" to "exported public", and this affects 277 and OSGi
in the same way. I don't think there is a conflict here.
- Stanley
