search

osgi / bugzilla-archive

Archive of OSGi Alliance Specification Bugzilla bugs. The Specification Bugzilla system was decommissioned with the move to GitHub. The issues in this repository are imported from the Specification Bugzilla system for archival purposes.
0 stars 1 forks source link

org.osgi.test.cases.framework.launch.secure is not correct #2993

Open bjhargrave opened 5 years ago

bjhargrave commented 5 years ago

Original bug ID: BZ#3125 From: Georgi Boyvalenkov <georgi.boyvalenkov@bosch-si.com> Reported version: R6

bjhargrave commented 5 years ago

Comment author: Georgi Boyvalenkov <georgi.boyvalenkov@bosch-si.com>

testFrameworkExtensionInvokerPermission fails, because bundle fragments.tb16a bundle cannot be started as expected. The reason is that this test bundle installs another test bundle on activation - fragments.tb16b and expects AccessControlException by catching it.

Actually the more generic SecurityException is thrown as described by spec.

bjhargrave commented 5 years ago

Comment author: @tjwatson

(In reply to Georgi Boyvalenkov from comment BZ#0)

testFrameworkExtensionInvokerPermission fails, because bundle fragments.tb16a bundle cannot be started as expected. The reason is that this test bundle installs another test bundle on activation - fragments.tb16b and expects AccessControlException by catching it.

Actually the more generic SecurityException is thrown as described by spec.

I agree, that is strange for the test to cache the AccessControlException instead of the general SecurityException.

bjhargrave commented 4 years ago

Comment author: @bjhargrave

CPEG call: Anjum, can you please fix?