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

[bjhargrave]

Original bug ID: BZ#3125
From: Georgi Boyvalenkov <[email protected]>
Reported version: R6

[bjhargrave]

Comment author: Georgi Boyvalenkov <[email protected]>

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]

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]

Comment author: @bjhargrave

CPEG call: Anjum, can you please fix?